Methods and systems for presenting alert event indicators

ABSTRACT

A method is performed at a client device with a display screen, processor(s), and memory storing program(s) for execution by the processor(s). The method comprises obtaining alert events from smart devices at a physical location. The smart devices include a camera located at or in proximity to the physical location. The method further comprises displaying in a scrollable list a chronological sequence of camera event items. Each of the camera event items includes a thumbnail image, a time of the alert event, and one or more activity alert indicators corresponding to predefined activity alert types. The method further comprises receiving a user selection of a first thumbnail image corresponding to a first one of the camera event items, and responsive to the user selection, enabling playback of a video of a first alert event in a video player interface while maintaining display of the scrollable list.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/385,944, titled “Methods and Systems for Presenting Alert EventIndicators,” filed Apr. 16, 2019, which is a continuation of U.S. patentapplication Ser. No. 15/194,528, titled “Methods and Systems forPresenting Alert Event Indicators,” filed Jun. 27, 2016, which is acontinuation of U.S. patent application Ser. No. 14/739,412, titled“Methods and Systems for Presenting Alert Event Indicators,” filed Jun.15, 2015, which is a continuation of U.S. patent application Ser. No.14/738,930, titled “Methods and Systems for Presenting Multiple LiveVideo Feeds in a User Interface,” filed Jun. 14, 2015, all of which arehereby incorporated by reference herein in their entirety.

This application is related to the following applications, which arehereby incorporated by reference herein in their entirety:

U.S. patent application Ser. No. 14/738,928, titled “Methods and Systemsfor Smart Home Automation Using a Multifunction Status and Entry PointIcon,” filed Jun. 14, 2015; and

U.S. patent application Ser. No. 14/739,427, titled “Methods and Systemsfor Presenting a Camera History,” filed Jun. 15, 2015.

TECHNICAL FIELD

The disclosed implementations relate generally to video monitoring,including, but not limited, to monitoring and reviewing video feeds andhistories of videos saved from the video feeds.

BACKGROUND

The advancement of internet and mobile technologies has enabled theadoption of remote video surveillance by users. Users can now monitor anarea under video surveillance using a website or a mobile application.Such websites or mobile apps typically allow a user to view live videoand/or saved video recordings, but otherwise provide little or noadditional information regarding the videos. Furthermore, the userinterfaces for viewing these live videos or saved video recordingsoccupy large amounts of display space and have a user control flow thatis poor at maintaining context for the user. Thus, more efficient,informative, and user-friendly presentations of live and saved videosurveillance are needed.

SUMMARY

Accordingly, there is a need for presentations of live and/or savedvideo with a more efficient user control flow and more usefulinformation. Such methods optionally complement or replace conventionalmethods for presenting live and/or saved video from video streams.

In accordance with some implementations, a method includes, in anapplication executing at a client device having one or more processorsand memory storing one or more programs for execution by the one or moreprocessors: receiving a plurality of video feeds, each video feed of theplurality of video feeds corresponding to a respective remote camera ofa plurality of remote cameras, where the video feeds are receivedconcurrently by the device from a server system communicatively coupledto the remote cameras; displaying a first user interface, the first userinterface including a plurality of user interface objects, each userinterface object of the plurality of user interface objects beingassociated with a respective remote camera of the remote cameras; anddisplaying in each user interface object of the plurality of userinterface objects the video feed corresponding to the respective remotecamera with which the user interface object is associated, where atleast one of the video feeds is displayed with cropping.

In accordance with some implementations, a method includes, at a serversystem having one or more processors and memory storing one or moreprograms for execution by the one or more processors: receiving a videofeed from a camera with an associated field of view; receiving one ormore alert events; identifying as a camera event a portion of the videofeed associated in time with the one or more alert events; determining astart time and a duration of the camera event; determining achronological order of the alert events; and saving, in a historyassociated with the camera, information associated with the cameraevent, including: a video clip and/or a frame from the portion of thevideo feed, and the chronological order of the alert events.

In accordance with some implementations, a method includes, at a clientdevice having one or more processors and memory storing one or moreprograms for execution by the one or more processors: displaying a videofeed from a camera or a frame from the video feed; and concurrently withdisplaying the video feed or the frame, displaying a camera historytimeline, including: displaying a representation of a camera eventassociated with one or more alert events in the camera history timelineas a bar overlaid on the event history timeline, the event bar having alength reflecting a duration of the camera event; and displaying,proximate to the event bar, one or more alert event indicators, each ofthe alert event indicators corresponding to a respective alert event ofthe alert events associated with the camera event, where each respectivealert event indicator has a respective visually distinctive displaycharacteristic associated with the corresponding respective alert event.

In accordance with some implementations, a method includes, at a clientdevice having one or more processors and memory storing one or moreprograms for execution by the one or more processors: displaying acamera history timeline, including: displaying a chronologically orderedsequence of event identifiers, each event identifier corresponding to arespective camera event, each respective camera event associated withone or more respective alert events; and displaying, for a respectiveevent identifier, one or more alert event indicators, each of the alertevent indicators corresponding to an alert event associated with thecamera event corresponding to the respective event identifier, each ofthe alert event indicators displayed with a visually distinctive displaycharacteristic associated with a corresponding alert event.

In accordance with some implementations, a method includes, at a clientdevice having one or more processors and memory storing one or moreprograms for execution by the one or more processors, in an applicationexecuting on the client device: displaying a camera event historyprovided by a remote server system, where the camera event history ispresented as a chronologically-ordered set of event identifiers, eachevent identifier corresponding to a respective event for which a remotecamera has captured an associated video; receiving a user selection of adisplayed event identifier; and in response to receiving the userselection of the displayed event identifier: expanding the selectedevent identifier into a video player window, the video player windowconsuming a portion of the displayed camera event history; and playing,in the video player window, the captured video associated with theselected event identifier; and in response to terminating playback ofthe captured video associated with the selected event identifier or userde-selection of the displayed event identifier, collapsing the videoplayer window into the selected event identifier thereby stopping theplaying of the captured video associated with the selected eventidentifier.

In accordance with some implementations, a system includes a pluralityof electronic devices, wherein at least one of the plurality ofelectronic devices has one or more processors and memory storing one ormore programs for execution by the processor, the one or more programsincluding instructions for performing the operations of the methoddescribed above. In accordance with some implementations, an electronicdevice has one or more processors and memory storing one or moreprograms for execution by the processor, the one or more programsincluding instructions for performing the operations of the methoddescribed above. In accordance with some implementations, a computerreadable storage medium has stored therein one or more programs havinginstructions which, when executed by an electronic device having one ormore processors, cause the electronic device to perform the operationsof the method described above.

Thus, computing systems are provided with more efficient methods forpresenting live and/or saved video and related information, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch systems. Such methods may complement or replace conventionalmethods for presenting live and/or saved video.

BRIEF DESCRIPTION OF THE DRAWINGS

The patent or application file contains at least one drawing executed incolor. Copies of this patent or patent application publication withcolor drawing(s) will be provided by the Office upon request and paymentof the necessary fee.

For a better understanding of the various described implementations,reference should be made to the Description of Implementations below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1 is an example smart home environment, in accordance with someimplementations.

FIG. 2 is a block diagram illustrating an example network architecturethat includes a smart home network, in accordance with someimplementations.

FIG. 3 illustrates a network-level view of an extensible devices andservices platform with which the smart home environment of FIG. 1 isintegrated, in accordance with some implementations.

FIG. 4 illustrates an abstracted functional view of the extensibledevices and services platform of FIG. 3, with reference to a processingengine as well as devices of the smart home environment, in accordancewith some implementations.

FIG. 5A is a representative operating environment in which a hub deviceserver system interacts with client devices and hub devicescommunicatively coupled to local smart devices, in accordance with someimplementations.

FIG. 5B is a representative operating environment in which a videoserver system interacts with client devices and hub devicescommunicatively coupled to local smart devices, in accordance with someimplementations.

FIG. 6 is a block diagram illustrating a representative hub device, inaccordance with some implementations.

FIG. 7A is a block diagram illustrating a representative hub deviceserver system, in accordance with some implementations.

FIG. 7B is a block diagram illustrating a representative video serversystem, in accordance with some implementations.

FIG. 7C is a block diagram illustrating a representative clientinterface server, in accordance with some implementations.

FIG. 7D is a block diagram illustrating a representative camerainterface server, in accordance with some implementations.

FIG. 8A-8B are block diagrams illustrating a representative clientdevice associated with a user account, in accordance with someimplementations.

FIG. 9A is a block diagram illustrating a representative smart device,in accordance with some implementations.

FIG. 9B is a block diagram illustrating a representative video capturingdevice (e.g., a camera) in accordance with some implementations.

FIG. 10 is a block diagram illustrating a representative smart homeprovider server system, in accordance with some implementations.

FIGS. 11A-11V illustrate example user interfaces on a client device formonitoring and reviewing video feeds in accordance with someimplementations.

FIGS. 12A-12E illustrate example user interfaces on a client device formonitoring and reviewing a video feed in accordance with someimplementations.

FIGS. 13A-13M illustrate example user interfaces on a client device forreviewing a camera history in accordance with some implementations.

FIGS. 14A-14E illustrate a flowchart diagram of a method for presentingmultiple video feeds in accordance with some implementations.

FIGS. 15A-15B illustrate a flowchart diagram of a method for savingalert events in a camera history in accordance with someimplementations.

FIGS. 16-17 illustrate flowchart diagrams of methods for presentingalert event indicators in accordance with some implementations.

FIGS. 18A-18B illustrate a flowchart diagram of a method for presentinga camera history in accordance with some implementations.

FIGS. 19A-19L illustrate example screenshots of user interfaces on aclient device in accordance with some implementations.

FIGS. 20A-20M illustrate example screenshots of user interfaces on aclient device in accordance with some implementations.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings.

DESCRIPTION OF IMPLEMENTATIONS

Reference will now be made in detail to implementations, examples ofwhich are illustrated in the accompanying drawings. In the followingdetailed description, numerous specific details are set forth in orderto provide a thorough understanding of the various describedimplementations. However, it will be apparent to one of ordinary skillin the art that the various described implementations may be practicedwithout these specific details. In other instances, well-known methods,procedures, components, circuits, and networks have not been describedin detail so as not to unnecessarily obscure aspects of theimplementations.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first userinterface could be termed a second user interface, and, similarly, asecond user interface could be termed a first user interface, withoutdeparting from the scope of the various described implementations. Thefirst user interface and the second user interface are both types ofuser interfaces, but they are not the same user interface.

The terminology used in the description of the various describedimplementations herein is for the purpose of describing particularimplementations only and is not intended to be limiting. As used in thedescription of the various described implementations and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting”or “in accordance with a determination that,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event]” or “in accordance with a determination that [astated condition or event] is detected,” depending on the context.

It is to be appreciated that “smart home environments” may refer tosmart environments for homes such as a single-family house, but thescope of the present teachings is not so limited. The present teachingsare also applicable, without limitation, to duplexes, townhomes,multi-unit apartment buildings, hotels, retail stores, office buildings,industrial buildings, and more generally any living space or work space.

It is also to be appreciated that while the terms user, customer,installer, homeowner, occupant, guest, tenant, landlord, repair person,and the like may be used to refer to the person or persons acting in thecontext of some particularly situations described herein, thesereferences do not limit the scope of the present teachings with respectto the person or persons who are performing such actions. Thus, forexample, the terms user, customer, purchaser, installer, subscriber, andhomeowner may often refer to the same person in the case of asingle-family residential dwelling, because the head of the household isoften the person who makes the purchasing decision, buys the unit, andinstalls and configures the unit, and is also one of the users of theunit. However, in other scenarios, such as a landlord-tenantenvironment, the customer may be the landlord with respect to purchasingthe unit, the installer may be a local apartment supervisor, a firstuser may be the tenant, and a second user may again be the landlord withrespect to remote control functionality. Importantly, while the identityof the person performing the action may be germane to a particularadvantage provided by one or more of the implementations, such identityshould not be construed in the descriptions that follow as necessarilylimiting the scope of the present teachings to those particularindividuals having those particular identities.

FIG. 1 is an example smart home environment 100 in accordance with someimplementations. Smart home environment 100 includes a structure 150(e.g., a house, office building, garage, or mobile home) with variousintegrated devices. It will be appreciated that devices may also beintegrated into a smart home environment 100 that does not include anentire structure 150, such as an apartment, condominium, or officespace. Further, the smart home environment 100 may control and/or becoupled to devices outside of the actual structure 150. Indeed, one ormore devices in the smart home environment 100 need not be physicallywithin the structure 150. For example, a device controlling a poolheater 114 or irrigation system 116 may be located outside of thestructure 150.

The depicted structure 150 includes a plurality of rooms 152, separatedat least partly from each other via walls 154. The walls 154 may includeinterior walls or exterior walls. Each room may further include a floor156 and a ceiling 158. Devices may be mounted on, integrated with and/orsupported by a wall 154, floor 156 or ceiling 158.

In some implementations, the integrated devices of the smart homeenvironment 100 include intelligent, multi-sensing, network-connecteddevices that integrate seamlessly with each other in a smart homenetwork (e.g., 202 FIG. 2) and/or with a central server or acloud-computing system to provide a variety of useful smart homefunctions. The smart home environment 100 may include one or moreintelligent, multi-sensing, network-connected thermostats 102(hereinafter referred to as “smart thermostats 102”), one or moreintelligent, network-connected, multi-sensing hazard detection units 104(hereinafter referred to as “smart hazard detectors 104”), one or moreintelligent, multi-sensing, network-connected entryway interface devices106 and 120 (hereinafter referred to as “smart doorbells 106” and “smartdoor locks 120”), and one or more intelligent, multi-sensing,network-connected alarm systems 122 (hereinafter referred to as “smartalarm systems 122”).

In some implementations, the one or more smart thermostats 102 detectambient climate characteristics (e.g., temperature and/or humidity) andcontrol a HVAC system 103 accordingly. For example, a respective smartthermostat 102 includes an ambient temperature sensor.

The one or more smart hazard detectors 104 may include thermal radiationsensors directed at respective heat sources (e.g., a stove, oven, otherappliances, a fireplace, etc.). For example, a smart hazard detector 104in a kitchen 153 includes a thermal radiation sensor directed at astove/oven 112. A thermal radiation sensor may determine the temperatureof the respective heat source (or a portion thereof) at which it isdirected and may provide corresponding blackbody radiation data asoutput.

The smart doorbell 106 and/or the smart door lock 120 may detect aperson's approach to or departure from a location (e.g., an outer door),control doorbell/door locking functionality (e.g., receive user inputsfrom a portable electronic device 166-1 to actuate bolt of the smartdoor lock 120), announce a person's approach or departure via audio orvisual means, and/or control settings on a security system (e.g., toactivate or deactivate the security system when occupants go and come).

The smart alarm system 122 may detect the presence of an individualwithin close proximity (e.g., using built-in IR sensors), sound an alarm(e.g., through a built-in speaker, or by sending commands to one or moreexternal speakers), and send notifications to entities or userswithin/outside of the smart home network 100. In some implementations,the smart alarm system 122 also includes one or more input devices orsensors (e.g., keypad, biometric scanner, NFC transceiver, microphone)for verifying the identity of a user, and one or more output devices(e.g., display, speaker). In some implementations, the smart alarmsystem 122 may also be set to an “armed” mode, such that detection of atrigger condition or event causes the alarm to be sounded unless adisarming action is performed.

In some implementations, the smart home environment 100 includes one ormore intelligent, multi-sensing, network-connected wall switches 108(hereinafter referred to as “smart wall switches 108”), along with oneor more intelligent, multi-sensing, network-connected wall pluginterfaces 110 (hereinafter referred to as “smart wall plugs 110”). Thesmart wall switches 108 may detect ambient lighting conditions, detectroom-occupancy states, and control a power and/or dim state of one ormore lights. In some instances, smart wall switches 108 may also controla power state or speed of a fan, such as a ceiling fan. The smart wallplugs 110 may detect occupancy of a room or enclosure and control supplyof power to one or more wall plugs (e.g., such that power is notsupplied to the plug if nobody is at home).

In some implementations, the smart home environment 100 of FIG. 1includes a plurality of intelligent, multi-sensing, network-connectedappliances 112 (hereinafter referred to as “smart appliances 112”), suchas refrigerators, stoves, ovens, televisions, washers, dryers, lights,stereos, intercom systems, garage-door openers, floor fans, ceilingfans, wall air conditioners, pool heaters, irrigation systems, securitysystems, space heaters, window AC units, motorized duct vents, and soforth. In some implementations, when plugged in, an appliance mayannounce itself to the smart home network, such as by indicating whattype of appliance it is, and it may automatically integrate with thecontrols of the smart home. Such communication by the appliance to thesmart home may be facilitated by either a wired or wirelesscommunication protocol. The smart home may also include a variety ofnon-communicating legacy appliances 140, such as old conventionalwasher/dryers, refrigerators, and the like, which may be controlled bysmart wall plugs 110. The smart home environment 100 may further includea variety of partially communicating legacy appliances 142, such asinfrared (“IR”) controlled wall air conditioners or other IR-controlleddevices, which may be controlled by IR signals provided by the smarthazard detectors 104 or the smart wall switches 108.

In some implementations, the smart home environment 100 includes one ormore network-connected cameras 118 that are configured to provide videomonitoring and security in the smart home environment 100. In someimplementations, cameras 118 also capture video when other conditions orhazards are detected, in order to provide visual monitoring of the smarthome environment 100 when those conditions or hazards occur. The cameras118 may be used to determine occupancy of the structure 150 and/orparticular rooms 152 in the structure 150, and thus may act as occupancysensors. For example, video captured by the cameras 118 may be processedto identify the presence of an occupant in the structure 150 (e.g., in aparticular room 152). Specific individuals may be identified based, forexample, on their appearance (e.g., height, face) and/or movement (e.g.,their walk/gait). For example, cameras 118 may additionally include oneor more sensors (e.g., IR sensors, motion detectors), input devices(e.g., microphone for capturing audio), and output devices (e.g.,speaker for outputting audio).

The smart home environment 100 may additionally or alternatively includeone or more other occupancy sensors (e.g., the smart doorbell 106, smartdoor locks 120, touch screens, IR sensors, microphones, ambient lightsensors, motion detectors, smart nightlights 170, etc.). In someimplementations, the smart home environment 100 includes radio-frequencyidentification (RFID) readers (e.g., in each room 152 or a portionthereof) that determine occupancy based on RFID tags located on orembedded in occupants. For example, RFID readers may be integrated intothe smart hazard detectors 104.

The smart home environment 100 may include one or more sound and/orvibration sensors for detecting abnormal sounds and/or vibrations. Thesesensors may be integrated with any of the devices described above. Thesound sensors detect sound above a decibel threshold. The vibrationsensors detect vibration above a threshold directed at a particular area(e.g., vibration on a particular window when a force is applied to breakthe window).

Conditions detected by the devices described above (e.g., motion, sound,vibrations, hazards) may be referred to collectively as alert events.

The smart home environment 100 may also include communication withdevices outside of the physical home but within a proximate geographicalrange of the home. For example, the smart home environment 100 mayinclude a pool heater monitor 114 that communicates a current pooltemperature to other devices within the smart home environment 100and/or receives commands for controlling the pool temperature.Similarly, the smart home environment 100 may include an irrigationmonitor 116 that communicates information regarding irrigation systemswithin the smart home environment 100 and/or receives controlinformation for controlling such irrigation systems.

By virtue of network connectivity, one or more of the smart home devicesof FIG. 1 may further allow a user to interact with the device even ifthe user is not proximate to the device. For example, a user maycommunicate with a device using a computer (e.g., a desktop computer,laptop computer, or tablet) or other portable electronic device 166(e.g., a mobile phone, such as a smart phone). A webpage or applicationmay be configured to receive communications from the user and controlthe device based on the communications and/or to present informationabout the device's operation to the user. For example, the user may viewa current set point temperature for a device (e.g., a stove) and adjustit using a computer. The user may be in the structure during this remotecommunication or outside the structure.

As discussed above, users may control smart devices in the smart homeenvironment 100 using a network-connected computer or portableelectronic device 166. In some examples, some or all of the occupants(e.g., individuals who live in the home) may register their device 166with the smart home environment 100. Such registration may be made at acentral server to authenticate the occupant and/or the device as beingassociated with the home and to give permission to the occupant to usethe device to control the smart devices in the home. An occupant may usetheir registered device 166 to remotely control the smart devices of thehome, such as when the occupant is at work or on vacation. The occupantmay also use their registered device to control the smart devices whenthe occupant is actually located inside the home, such as when theoccupant is sitting on a couch inside the home. It should be appreciatedthat instead of or in addition to registering devices 166, the smarthome environment 100 may make inferences about which individuals live inthe home and are therefore occupants and which devices 166 areassociated with those individuals. As such, the smart home environmentmay “learn” who is an occupant and permit the devices 166 associatedwith those individuals to control the smart devices of the home.

In some implementations, in addition to containing processing andsensing capabilities, devices 102, 104, 106, 108, 110, 112, 114, 116,118, 120, and/or 122 (collectively referred to as “the smart devices”)are capable of data communications and information sharing with othersmart devices, a central server or cloud-computing system, and/or otherdevices that are network-connected. Data communications may be carriedout using any of a variety of custom or standard wireless protocols(e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, BluetoothSmart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety ofcustom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), orany other suitable communication protocol, including communicationprotocols not yet developed as of the filing date of this document.

In some implementations, the smart devices serve as wireless or wiredrepeaters. In some implementations, a first one of the smart devicescommunicates with a second one of the smart devices via a wirelessrouter. The smart devices may further communicate with each other via aconnection (e.g., network interface 160) to a network, such as theInternet 162. Through the Internet 162, the smart devices maycommunicate with a smart home provider server system 164 (also called acentral server system and/or a cloud-computing system herein). The smarthome provider server system 164 may be associated with a manufacturer,support entity, or service provider associated with the smart device(s).In some implementations, a user is able to contact customer supportusing a smart device itself rather than needing to use othercommunication means, such as a telephone or Internet-connected computer.In some implementations, software updates are automatically sent fromthe smart home provider server system 164 to smart devices (e.g., whenavailable, when purchased, or at routine intervals).

In some implementations, the network interface 160 includes aconventional network device (e.g., a router), and the smart homeenvironment 100 of FIG. 1 includes a hub device 180 that iscommunicatively coupled to the network(s) 162 directly or via thenetwork interface 160. The hub device 180 is further communicativelycoupled to one or more of the above intelligent, multi-sensing,network-connected devices (e.g., smart devices of the smart homeenvironment 100). Each of these smart devices optionally communicateswith the hub device 180 using one or more radio communication networksavailable at least in the smart home environment 100 (e.g., ZigBee,Z-Wave, Insteon, Bluetooth, Wi-Fi and other radio communicationnetworks). In some implementations, the hub device 180 and devicescoupled with/to the hub device can be controlled and/or interacted withvia an application running on a smart phone, household controller,laptop, tablet computer, game console or similar electronic device. Insome implementations, a user of such controller application can viewstatus of the hub device or coupled smart devices, configure the hubdevice to interoperate with smart devices newly introduced to the homenetwork, commission new smart devices, and adjust or view settings ofconnected smart devices, etc. In some implementations the hub deviceextends capabilities of low capability smart device to matchcapabilities of the highly capable smart devices of the same type,integrates functionality of multiple different device types—even acrossdifferent communication protocols, and is configured to streamlineadding of new devices and commissioning of the hub device.

FIG. 2 is a block diagram illustrating an example network architecture200 that includes a smart home network 202 in accordance with someimplementations. In some implementations, the smart devices 204 in thesmart home environment 100 (e.g., devices 102, 104, 106, 108, 110, 112,114, 116, 118, 120, and/or 122) combine with the hub device 180 tocreate a mesh network in smart home network 202. In someimplementations, one or more smart devices 204 in the smart home network202 operate as a smart home controller. Additionally and/oralternatively, hub device 180 operates as the smart home controller. Insome implementations, a smart home controller has more computing powerthan other smart devices. In some implementations, a smart homecontroller processes inputs (e.g., from smart devices 204, electronicdevice 166, and/or smart home provider server system 164) and sendscommands (e.g., to smart devices 204 in the smart home network 202) tocontrol operation of the smart home environment 100. In someimplementations, some of the smart devices 204 in the smart home network202 (e.g., in the mesh network) are “spokesman” nodes (e.g., 204-1) andothers are “low-powered” nodes (e.g., 204-9). Some of the smart devicesin the smart home environment 100 are battery powered, while others havea regular and reliable power source, such as by connecting to wiring(e.g., to 120V line voltage wires) behind the walls 154 of the smarthome environment. The smart devices that have a regular and reliablepower source are referred to as “spokesman” nodes. These nodes aretypically equipped with the capability of using a wireless protocol tofacilitate bidirectional communication with a variety of other devicesin the smart home environment 100, as well as with the smart homeprovider server system 164. In some implementations, one or more“spokesman” nodes operate as a smart home controller. On the other hand,the devices that are battery powered are the “low-power” nodes. Thesenodes tend to be smaller than spokesman nodes and typically onlycommunicate using wireless protocols that require very little power,such as Zigbee, 6LoWPAN, etc.

In some implementations, some low-power nodes are incapable ofbidirectional communication. These low-power nodes send messages, butthey are unable to “listen”. Thus, other devices in the smart homeenvironment 100, such as the spokesman nodes, cannot send information tothese low-power nodes.

In some implementations, some low-power nodes are capable of only alimited bidirectional communication. For example, other devices are ableto communicate with the low-power nodes only during a certain timeperiod.

As described, in some implementations, the smart devices serve aslow-power and spokesman nodes to create a mesh network in the smart homeenvironment 100. In some implementations, individual low-power nodes inthe smart home environment regularly send out messages regarding whatthey are sensing, and the other low-powered nodes in the smart homeenvironment—in addition to sending out their own messages—forward themessages, thereby causing the messages to travel from node to node(i.e., device to device) throughout the smart home network 202. In someimplementations, the spokesman nodes in the smart home network 202,which are able to communicate using a relatively high-powercommunication protocol, such as IEEE 802.11, are able to switch to arelatively low-power communication protocol, such as IEEE 802.15.4, toreceive these messages, translate the messages to other communicationprotocols, and send the translated messages to other spokesman nodesand/or the smart home provider server system 164 (using, e.g., therelatively high-power communication protocol). Thus, the low-powerednodes using low-power communication protocols are able to send and/orreceive messages across the entire smart home network 202, as well asover the Internet 162 to the smart home provider server system 164. Insome implementations, the mesh network enables the smart home providerserver system 164 to regularly receive data from most or all of thesmart devices in the home, make inferences based on the data, facilitatestate synchronization across devices within and outside of the smarthome network 202, and send commands to one or more of the smart devicesto perform tasks in the smart home environment.

As described, the spokesman nodes and some of the low-powered nodes arecapable of “listening.” Accordingly, users, other devices, and/or thesmart home provider server system 164 may communicate control commandsto the low-powered nodes. For example, a user may use the electronicdevice 166 (e.g., a smart phone) to send commands over the Internet tothe smart home provider server system 164, which then relays thecommands to one or more spokesman nodes in the smart home network 202.The spokesman nodes may use a low-power protocol to communicate thecommands to the low-power nodes throughout the smart home network 202,as well as to other spokesman nodes that did not receive the commandsdirectly from the smart home provider server system 164.

In some implementations, a smart nightlight 170 (FIG. 1), which is anexample of a smart device 204, is a low-power node. In addition tohousing a light source, the smart nightlight 170 houses an occupancysensor, such as an ultrasonic or passive IR sensor, and an ambient lightsensor, such as a photo resistor or a single-pixel sensor that measureslight in the room. In some implementations, the smart nightlight 170 isconfigured to activate the light source when its ambient light sensordetects that the room is dark and when its occupancy sensor detects thatsomeone is in the room. In other implementations, the smart nightlight170 is simply configured to activate the light source when its ambientlight sensor detects that the room is dark. Further, in someimplementations, the smart nightlight 170 includes a low-power wirelesscommunication chip (e.g., a ZigBee chip) that regularly sends outmessages regarding the occupancy of the room and the amount of light inthe room, including instantaneous messages coincident with the occupancysensor detecting the presence of a person in the room. As mentionedabove, these messages may be sent wirelessly (e.g., using the meshnetwork) from node to node (i.e., smart device to smart device) withinthe smart home network 202 as well as over the Internet 162 to the smarthome provider server system 164.

Other examples of low-power nodes include battery-operated versions ofthe smart hazard detectors 104. These smart hazard detectors 104 areoften located in an area without access to constant and reliable powerand may include any number and type of sensors, such as smoke/fire/heatsensors (e.g., thermal radiation sensors), carbon monoxide/dioxidesensors, occupancy/motion sensors, ambient light sensors, ambienttemperature sensors, humidity sensors, and the like. Furthermore, smarthazard detectors 104 may send messages that correspond to each of therespective sensors to the other devices and/or the smart home providerserver system 164, such as by using the mesh network as described above.

Examples of spokesman nodes include smart doorbells 106, smartthermostats 102, smart wall switches 108, and smart wall plugs 110.These devices are often located near and connected to a reliable powersource, and therefore may include more power-consuming components, suchas one or more communication chips capable of bidirectionalcommunication in a variety of protocols.

In some implementations, the smart home environment 100 includes servicerobots 168 (FIG. 1) that are configured to carry out, in an autonomousmanner, any of a variety of household tasks.

As explained above with reference to FIG. 1, in some implementations,the smart home environment 100 of FIG. 1 includes a hub device 180 thatis communicatively coupled to the network(s) 162 directly or via thenetwork interface 160. The hub device 180 is further communicativelycoupled to one or more of the smart devices using a radio communicationnetwork that is available at least in the smart home environment 100.Communication protocols used by the radio communication network include,but are not limited to, ZigBee, Z-Wave, Insteon, EuOcean, Thread, OSIAN,Bluetooth Low Energy and the like. In some implementations, the hubdevice 180 not only converts the data received from each smart device tomeet the data format requirements of the network interface 160 or thenetwork(s) 162, but also converts information received from the networkinterface 160 or the network(s) 162 to meet the data format requirementsof the respective communication protocol associated with a targetedsmart device. In some implementations, in addition to data formatconversion, the hub device 180 further processes the data received fromthe smart devices or information received from the network interface 160or the network(s) 162 preliminary. For example, the hub device 180 canintegrate inputs from multiple sensors/connected devices (includingsensors/devices of the same and/or different types), perform higherlevel processing on those inputs—e.g., to assess the overall environmentand coordinate operation among the different sensors/devices—and/orprovide instructions to the different devices based on the collection ofinputs and programmed processing. It is also noted that in someimplementations, the network interface 160 and the hub device 180 areintegrated to one network device. Functionality described herein isrepresentative of particular implementations of smart devices, controlapplication(s) running on representative electronic device(s) (such as asmart phone), hub device(s) 180, and server(s) coupled to hub device(s)via the Internet or other Wide Area Network. All or a portion of thisfunctionality and associated operations can be performed by any elementsof the described system—for example, all or a portion of thefunctionality described herein as being performed by an implementationof the hub device can be performed, in different system implementations,in whole or in part on the server, one or more connected smart devicesand/or the control application, or different combinations thereof.

FIG. 3 illustrates a network-level view of an extensible devices andservices platform with which the smart home environment of FIG. 1 isintegrated, in accordance with some implementations. The extensibledevices and services platform 300 includes smart home provider serversystem 164. Each of the intelligent, network-connected devices describedwith reference to FIG. 1 (e.g., 102, 104, 106, 108, 110, 112, 114, 116and 118, identified simply as “devices” in FIGS. 2-4) may communicatewith the smart home provider server system 164. For example, aconnection to the Internet 162 may be established either directly (forexample, using 3G/4G connectivity to a wireless carrier), or through anetwork interface 160 (e.g., a router, switch, gateway, hub device, oran intelligent, dedicated whole-home controller node), or through anycombination thereof.

In some implementations, the devices and services platform 300communicates with and collects data from the smart devices of the smarthome environment 100. In addition, in some implementations, the devicesand services platform 300 communicates with and collects data from aplurality of smart home environments across the world. For example, thesmart home provider server system 164 collects home data 302 from thedevices of one or more smart home environments 100, where the devicesmay routinely transmit home data or may transmit home data in specificinstances (e.g., when a device queries the home data 302). Examplecollected home data 302 includes, without limitation, power consumptiondata, blackbody radiation data, occupancy data, HVAC settings and usagedata, carbon monoxide levels data, carbon dioxide levels data, volatileorganic compounds levels data, sleeping schedule data, cooking scheduledata, inside and outside temperature humidity data, televisionviewership data, inside and outside noise level data, pressure data,video data, etc.

In some implementations, the smart home provider server system 164provides one or more services 304 to smart homes and/or third parties.Example services 304 include, without limitation, software updates,customer support, sensor data collection/logging, remote access, remoteor distributed control, and/or use suggestions (e.g., based on collectedhome data 302) to improve performance, reduce utility cost, increasesafety, etc. In some implementations, data associated with the services304 is stored at the smart home provider server system 164, and thesmart home provider server system 164 retrieves and transmits the dataat appropriate times (e.g., at regular intervals, upon receiving arequest from a user, etc.).

In some implementations, the extensible devices and services platform300 includes a processing engine 306, which may be concentrated at asingle server or distributed among several different computing entitieswithout limitation. In some implementations, the processing engine 306includes engines configured to receive data from the devices of smarthome environments 100 (e.g., via the Internet 162 and/or a networkinterface 160), to index the data, to analyze the data and/or togenerate statistics based on the analysis or as part of the analysis. Insome implementations, the analyzed data is stored as derived home data308.

Results of the analysis or statistics may thereafter be transmitted backto the device that provided home data used to derive the results, toother devices, to a server providing a webpage to a user of the device,or to other non-smart device entities. In some implementations, usagestatistics, usage statistics relative to use of other devices, usagepatterns, and/or statistics summarizing sensor readings are generated bythe processing engine 306 and transmitted. The results or statistics maybe provided via the Internet 162. In this manner, the processing engine306 may be configured and programmed to derive a variety of usefulinformation from the home data 302. A single server may include one ormore processing engines.

The derived home data 308 may be used at different granularities for avariety of useful purposes, ranging from explicit programmed control ofthe devices on a per-home, per-neighborhood, or per-region basis (forexample, demand-response programs for electrical utilities), to thegeneration of inferential abstractions that may assist on a per-homebasis (for example, an inference may be drawn that the homeowner hasleft for vacation and so security detection equipment may be put onheightened sensitivity), to the generation of statistics and associatedinferential abstractions that may be used for government or charitablepurposes. For example, processing engine 306 may generate statisticsabout device usage across a population of devices and send thestatistics to device users, service providers or other entities (e.g.,entities that have requested the statistics and/or entities that haveprovided monetary compensation for the statistics).

In some implementations, to encourage innovation and research and toincrease products and services available to users, the devices andservices platform 300 exposes a range of application programminginterfaces (APIs) 310 to third parties, such as charities 314,governmental entities 316 (e.g., the Food and Drug Administration or theEnvironmental Protection Agency), academic institutions 318 (e.g.,university researchers), businesses 320 (e.g., providing devicewarranties or service to related equipment, targeting advertisementsbased on home data), utility companies 324, and other third parties. TheAPIs 310 are coupled to and permit third-party systems to communicatewith the smart home provider server system 164, including the services304, the processing engine 306, the home data 302, and the derived homedata 308. In some implementations, the APIs 310 allow applicationsexecuted by the third parties to initiate specific data processing tasksthat are executed by the smart home provider server system 164, as wellas to receive dynamic updates to the home data 302 and the derived homedata 308.

For example, third parties may develop programs and/or applications(e.g., web applications or mobile applications) that integrate with thesmart home provider server system 164 to provide services andinformation to users. Such programs and applications may be, forexample, designed to help users reduce energy consumption, topreemptively service faulty equipment, to prepare for high servicedemands, to track past service performance, etc., and/or to performother beneficial functions or tasks.

FIG. 4 illustrates an abstracted functional view 400 of the extensibledevices and services platform 300 of FIG. 3, with reference to aprocessing engine 306 as well as devices of the smart home environment,in accordance with some implementations. Even though devices situated insmart home environments will have a wide variety of different individualcapabilities and limitations, the devices may be thought of as sharingcommon characteristics in that each device is a data consumer 402 (DC),a data source 404 (DS), a services consumer 406 (SC), and a servicessource 408 (SS). Advantageously, in addition to providing controlinformation used by the devices to achieve their local and immediateobjectives, the extensible devices and services platform 300 may also beconfigured to use the large amount of data that is generated by thesedevices. In addition to enhancing or optimizing the actual operation ofthe devices themselves with respect to their immediate functions, theextensible devices and services platform 300 may be directed to“repurpose” that data in a variety of automated, extensible, flexible,and/or scalable ways to achieve a variety of useful objectives. Theseobjectives may be predefined or adaptively identified based on, e.g.,usage patterns, device efficiency, and/or user input (e.g., requestingspecific functionality).

FIG. 4 shows processing engine 306 as including a number of processingparadigms 410. In some implementations, processing engine 306 includes amanaged services paradigm 410 a that monitors and manages primary orsecondary device functions. The device functions may include ensuringproper operation of a device given user inputs, estimating that (e.g.,and responding to an instance in which) an intruder is or is attemptingto be in a dwelling, detecting a failure of equipment coupled to thedevice (e.g., a light bulb having burned out), implementing or otherwiseresponding to energy demand response events, providing a heat-sourcealert, and/or alerting a user of a current or predicted future event orcharacteristic. In some implementations, processing engine 306 includesan advertising/communication paradigm 410 b that estimatescharacteristics (e.g., demographic information), desires and/or productsof interest of a user based on device usage. Services, promotions,products or upgrades may then be offered or automatically provided tothe user. In some implementations, processing engine 306 includes asocial paradigm 410 c that uses information from a social network,provides information to a social network (for example, based on deviceusage), and/or processes data associated with user and/or deviceinteractions with the social network platform. For example, a user'sstatus as reported to their trusted contacts on the social network maybe updated to indicate when the user is home based on light detection,security system inactivation or device usage detectors. As anotherexample, a user may be able to share device-usage statistics with otherusers. In yet another example, a user may share HVAC settings thatresult in low power bills and other users may download the HVAC settingsto their smart thermostat 102 to reduce their power bills.

In some implementations, processing engine 306 includes achallenges/rules/compliance/rewards paradigm 410 d that informs a userof challenges, competitions, rules, compliance regulations and/orrewards and/or that uses operation data to determine whether a challengehas been met, a rule or regulation has been complied with and/or areward has been earned. The challenges, rules, and/or regulations mayrelate to efforts to conserve energy, to live safely (e.g., reducing theoccurrence of heat-source alerts) (e.g., reducing exposure to toxins orcarcinogens), to conserve money and/or equipment life, to improvehealth, etc. For example, one challenge may involve participants turningdown their thermostat by one degree for one week. Those participantsthat successfully complete the challenge are rewarded, such as withcoupons, virtual currency, status, etc. Regarding compliance, an exampleinvolves a rental-property owner making a rule that no renters arepermitted to access certain owner's rooms. The devices in the roomhaving occupancy sensors may send updates to the owner when the room isaccessed.

In some implementations, processing engine 306 integrates or otherwiseuses extrinsic information 412 from extrinsic sources to improve thefunctioning of one or more processing paradigms. Extrinsic information412 may be used to interpret data received from a device, to determine acharacteristic of the environment near the device (e.g., outside astructure that the device is enclosed in), to determine services orproducts available to the user, to identify a social network orsocial-network information, to determine contact information of entities(e.g., public-service entities such as an emergency-response team, thepolice or a hospital) near the device, to identify statistical orenvironmental conditions, trends or other information associated with ahome or neighborhood, and so forth.

FIG. 5A illustrates a representative operating environment 500 in whicha hub device server system 508 provides data processing for monitoringand facilitating review of alert events (e.g., motion events) in videostreams captured by video cameras 118. As shown in FIG. 5A, the hubdevice server system 508 receives video data from video sources 522(including cameras 118) located at various physical locations (e.g.,inside homes, restaurants, stores, streets, parking lots, and/or thesmart home environments 100 of FIG. 1). Each video source 522 may bebound to one or more user (e.g., reviewer) accounts, and the hub deviceserver system 508 provides video monitoring data for the video source522 to client devices 504 associated with the reviewer accounts. Forexample, the portable electronic device 166 is an example of the clientdevice 504.

In some implementations, the smart home provider server system 164 or acomponent thereof serves as the hub device server system 508; the hubdevice server system 508 is a part or component of the smart homeprovider server system 164. In some implementations, the hub deviceserver system 508 is a dedicated video processing server that providesvideo processing services to video sources and client devices 504independent of other services provided by the hub device server system508. An example of a video processing server is described below withreference to FIG. 5B.

In some implementations, each of the video sources 522 includes one ormore video cameras 118 that capture video and send the captured video tothe hub device server system 508 substantially in real-time. In someimplementations, each of the video sources 522 optionally includes acontroller device (not shown) that serves as an intermediary between theone or more cameras 118 and the hub device server system 508. Thecontroller device receives the video data from the one or more cameras118, optionally performs some preliminary processing on the video data,and sends the video data to the hub device server system 508 on behalfof the one or more cameras 118 substantially in real-time. In someimplementations, each camera has its own on-board processingcapabilities to perform some preliminary processing on the capturedvideo data before sending the processed video data (along with metadataobtained through the preliminary processing) to the controller deviceand/or the hub device server system 508.

In some implementations, a camera 118 of a video source 522 capturesvideo at a first resolution (e.g., 720P and/or 1080P) and/or a firstframe rate (24 frames per second), and sends the captured video to thehub device server system 508 at both the first resolution (e.g., theoriginal capture resolution(s), the high-quality resolution(s) such as1080P and/or 720P) and the first frame rate, and at a second, differentresolution (e.g., 180P) and/or a second frame rate (e.g., 5 frames persecond or 10 frames per second). For example, the camera 118 captures avideo 523-1 at 720P and/or 1080P resolution (the camera 118 may capturea video at 1080P and create a downscaled 720P version, or capture atboth 720P and 1080P). The video source 522 creates a second (or third),rescaled (and optionally at a different frame rate than the version523-1) version 525-1 of the captured video at 180P resolution, andtransmits both the original captured version 523-1 (i.e., 1080P and/or720P) and the rescaled version 525-1 (i.e., the 180P version) to the hubdevice server system 508 for storage. In some implementations, therescaled version has a lower resolution, and optionally a lower framerate, than the original captured video. The hub device server system 508transmits the original captured version or the rescaled version to aclient 504, depending on the context. For example, the hub device serversystem 508 transmits the rescaled version when transmitting multiplevideos to the same client device 504 for concurrent monitoring by theuser, and transmits the original captured version in other contexts. Insome implementations, the hub device server system 508 downscales theoriginal captured version to a lower resolution, and transmits thedownscaled version.

In some other implementations, a camera 118 of a video source 522captures video at a first resolution (e.g., 720P and/or 1080P) and/or afirst frame rate, and sends the captured video to the hub device serversystem 508 at the first resolution (e.g., the original captureresolution(s); the high-quality resolution(s) such as 1080P and/or 720P)and first frame rate for storage. When the hub device server system 508transmits the video to a client device, the hub device server system 508may downscale the video to a second, lower resolution (e.g., 180P)and/or second, lower frame rate for the transmission, depending on thecontext. For example, the hub device server system 508 transmits thedownscaled version when transmitting multiple videos to the same clientdevice 504 for concurrent monitoring by the user, and transmits theoriginal captured version in other contexts.

As shown in FIG. 5A, in accordance with some implementations, each ofthe client devices 504 includes a client-side module 502. Theclient-side module 502 communicates with a server-side module 506executed on the hub device server system 508 through the one or morenetworks 162. The client-side module 502 provides client-sidefunctionalities for the event monitoring and review processing andcommunications with the server-side module 506. The server-side module506 provides server-side functionalities for event monitoring and reviewprocessing for any number of client-side modules 502 each residing on arespective client device 504. The server-side module 506 also providesserver-side functionalities for video processing and camera control forany number of the video sources 522, including any number of controldevices and the cameras 118.

In some implementations, the server-side module 506 includes one or moreprocessors 512, a video storage database 514, device and accountdatabases 516, an I/O interface to one or more client devices 518, andan I/O interface to one or more video sources 520. The I/O interface toone or more clients 518 facilitates the client-facing input and outputprocessing for the server-side module 506. In some implementations, theI/O interface to clients 518 or a transcoding proxy computer (not shown)rescales (e.g., downscales) and/or changes the frame rate of video fortransmission to a client 504. The databases 516 store a plurality ofprofiles for reviewer accounts registered with the video processingserver, where a respective user profile includes account credentials fora respective reviewer account, and one or more video sources linked tothe respective reviewer account. The I/O interface to one or more videosources 520 facilitates communications with one or more video sources522 (e.g., groups of one or more cameras 118 and associated controllerdevices). The video storage database 514 stores raw video data receivedfrom the video sources 522, as well as various types of metadata, suchas motion events, event categories, event category models, eventfilters, and event masks, for use in data processing for eventmonitoring and review for each reviewer account.

In some implementations, the server-side module 506 receives informationregarding alert events detected by other smart devices 204 (e.g.,hazards, sound, vibration, motion). In accordance with the alert eventinformation, the server-side module 506 instructs one or more videosources 522 in the smart home environment 100 where the alert event isdetected to capture video and/or associate with the alert event video,received from the video sources 522 in the same smart home environment100, that is contemporaneous or proximate in time with the alert event.

Examples of a representative client device 504 include, but are notlimited to, a handheld computer, a wearable computing device, a personaldigital assistant (PDA), a tablet computer, a laptop computer, a desktopcomputer, a cellular telephone, a smart phone, an enhanced generalpacket radio service (EGPRS) mobile phone, a media player, a navigationdevice, a game console, a television, a remote control, a point-of-sale(POS) terminal, vehicle-mounted computer, an ebook reader, or acombination of any two or more of these data processing devices or otherdata processing devices. For example, client devices 504-1, 504-2, and504-m are a smart phone, a tablet computer, and a laptop computer,respectively.

Examples of the one or more networks 162 include local area networks(LAN) and wide area networks (WAN) such as the Internet. The one or morenetworks 162 are, optionally, implemented using any known networkprotocol, including various wired or wireless protocols, such asEthernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution(LTE), Global System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), code division multiple access (CDMA), time divisionmultiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol(VoIP), Wi-MAX, or any other suitable communication protocol.

In some implementations, the hub device server system 508 is implementedon one or more standalone data processing apparatuses or a distributednetwork of computers. In some implementations, the hub device serversystem 508 also employs various virtual devices and/or services of thirdparty service providers (e.g., third-party cloud service providers) toprovide the underlying computing resources and/or infrastructureresources of the hub device server system 508. In some implementations,the hub device server system 508 includes, but is not limited to, ahandheld computer, a tablet computer, a laptop computer, a desktopcomputer, or a combination of any two or more of these data processingdevices or other data processing devices.

The server-client environment 500 shown in FIG. 5A includes both aclient-side portion (e.g., the client-side module 502) and a server-sideportion (e.g., the server-side module 506). The division offunctionalities between the client and server portions of operatingenvironment 500 can vary in different implementations. Similarly, thedivision of functionalities between the video source 522 and the hubdevice server system 508 can vary in different implementations. Forexample, in some implementations, client-side module 502 is athin-client that provides only user-facing input and output processingfunctions, and delegates all other data processing functionalities to abackend server (e.g., the hub device server system 508). Similarly, insome implementations, a respective one of the video sources 522 is asimple video capturing device that continuously captures and streamsvideo data to the hub device server system 508 with no or limited localpreliminary processing on the video data. Although many aspects of thepresent technology are described from the perspective of the hub deviceserver system 508, the corresponding actions performed by the clientdevice 504 and/or the video sources 522 would be apparent to onesskilled in the art without any creative efforts. Similarly, some aspectsof the present technology may be described from the perspective of theclient device or the video source, and the corresponding actionsperformed by the video server would be apparent to ones skilled in theart without any creative efforts. Furthermore, some aspects of thepresent technology may be performed by the hub device server system 508,the client device 504, and the video sources 522 cooperatively.

It should be understood that operating environment 500 that involves thehub device server system 508, the video sources 522 and the videocameras 118 is merely an example. Many aspects of operating environment500 are generally applicable in other operating environments in which aserver system provides data processing for monitoring and facilitatingreview of data captured by other types of electronic devices (e.g.,smart thermostats 102, smart hazard detectors 104, smart doorbells 106,smart wall plugs 110, appliances 112 and the like).

The electronic devices, the client devices or the server systemcommunicate with each other using the one or more communication networks162. In an example smart home environment, two or more devices (e.g.,the network interface device 160, the hub device 180, and the clientdevices 504-m) are located in close proximity to each other, such thatthey could be communicatively coupled in the same sub-network 162A viawired connections, a WLAN or a Bluetooth Personal Area Network (PAN).The Bluetooth PAN is optionally established based on classical Bluetoothtechnology or Bluetooth Low Energy (BLE) technology. This smart homeenvironment further includes one or more other radio communicationnetworks 162B through which at least some of the electronic devices ofthe video sources 522-n exchange data with the hub device 180.Alternatively, in some situations, some of the electronic devices of thevideo sources 522-n communicate with the network interface device 160directly via the same sub-network 162A that couples devices 160, 180 and504-m. In some implementations (e.g., in the network 162C), both theclient device 504-m and the electronic devices of the video sources522-n communicate directly via the network(s) 162 without passing thenetwork interface device 160 or the hub device 180.

In some implementations, during normal operation, the network interfacedevice 160 and the hub device 180 communicate with each other to form anetwork gateway through which data are exchanged with the electronicdevice of the video sources 522-n. As explained above, the networkinterface device 160 and the hub device 180 optionally communicate witheach other via a sub-network 162A.

In some implementations, the hub device 180 is omitted, and thefunctionality of the hub device 180 is performed by the hub deviceserver system 508, video server system 552, or smart home providerserver system 164.

In some implementations, the hub device server system 508 is, orincludes, a dedicated video processing server. FIG. 5B illustrates arepresentative operating environment 550 in which a video server system552 serves as a dedicated video processing server and provides dataprocessing for monitoring and facilitating review of alert events (e.g.,motion events) in video streams captured by video cameras 118. As shownin FIG. 5B, the video server system 552 receives video data from videosources 522 (including cameras 118) located at various physicallocations (e.g., inside homes, restaurants, stores, streets, parkinglots, and/or the smart home environments 100 of FIG. 1). Each videosource 522 may be bound to one or more user (e.g., reviewer) accounts,and the video server system 552 provides video monitoring data for thevideo source 522 to client devices 504 associated with the revieweraccounts. For example, the portable electronic device 166 is an exampleof the client device 504.

In some implementations, the smart home provider server system 164 or acomponent thereof serves as the video server system 552; the videoserver system 552 is a part or component of the smart home providerserver system 164. In some implementations, the video server system 552is separate from the smart home provider server system 164, and providesvideo processing services to video sources 522 and client devices 504independent of other services provided by the smart home provider serversystem 164. In some implementations, the smart home provider serversystem 164 and the video server system 552 are separate but communicateinformation with each other to provide functionality to users. Forexample, a detection of a hazard may be communicated by the smart homeprovider server system 164 to the video server system 552, and the videoserver system 552, in accordance with the communication regarding thedetection of the hazard, records, processes, and/or provides videoassociated with the detected hazard.

In some implementations, each of the video sources 522 includes one ormore video cameras 118 that capture video and send the captured video tothe video server system 552 substantially in real-time. In someimplementations, each of the video sources 522 optionally includes acontroller device (not shown) that serves as an intermediary between theone or more cameras 118 and the video server system 552. The controllerdevice receives the video data from the one or more cameras 118,optionally, performs some preliminary processing on the video data, andsends the video data to the video server system 552 on behalf of the oneor more cameras 118 substantially in real-time. In some implementations,each camera has its own on-board processing capabilities to perform somepreliminary processing on the captured video data before sending theprocessed video data (along with metadata obtained through thepreliminary processing) to the controller device and/or the video serversystem 552.

In some implementations, a camera 118 of a video source 522 capturesvideo at a first resolution (e.g., 720P and/or 1080P) and/or a firstframe rate (24 frames per second), and sends the captured video to thevideo server system 552 at both the first resolution (e.g., the originalcapture resolution(s), the high-quality resolution(s)) and the firstframe rate, and a second, different resolution (e.g., 180P) and/or asecond frame rate (e.g., 5 frames per second or 10 frames per second).For example, the camera 118 captures a video 523-1 at 720P and/or 1080Presolution (the camera 118 may capture a video at 1080P and create adownscaled 720P version, or capture at both 720P and 1080P). The videosource 522 creates a second (or third), rescaled (and optionally at adifferent frame rate than the version 523-1) version 525-1 of thecaptured video at 180P resolution, and transmits both the originalcaptured version 523-1 (i.e., 1080P and/or 720P) and the rescaledversion 525-1 (i.e., the 180P version) to the video server system 552for storage. In some implementations, the rescaled version has a lowerresolution, and optionally a lower frame rate, than the originalcaptured video. The video server system 552 transmits the originalcaptured version or the rescaled version to a client 504, depending onthe context. For example, the video server system 552 transmits therescaled version when transmitting multiple videos to the same clientdevice 504 for concurrent monitoring by the user, and transmits theoriginal captured version in other contexts. In some implementations,the video server system 552 downscales the original captured version toa lower resolution, and transmits the downscaled version.

In some other implementations, a camera 118 of a video source 522captures video at a first resolution (e.g., 720P and/or 1080P)) and/or afirst frame rate, and sends the captured video to the video serversystem 552 at the first resolution (e.g., the original captureresolution(s), the high-quality resolution(s) such as 1080P and/or 720P)and the first fame rate for storage. When the video server system 552transmits the video to a client device, the video server system 552 maydownscale the video to a second, lower resolution (e.g., 180P) and/orsecond, lower frame rate for the transmission, depending on the context.For example, the video server system 552 transmits the downscaledversion when transmitting multiple videos to the same client device 504for concurrent monitoring by the user, and transmits the originalcaptured version in other contexts.

As shown in FIG. 5B, in accordance with some implementations, each ofthe client devices 504 includes a client-side module 502. Theclient-side module 502 communicates with the video server system 552through the one or more networks 162. In some implementations, the videoserver system 552 includes a video server 552, a client interface server556, and a camera interface server 558. In some implementations, thevideo server 552 includes the server-side module 506 and its componentsand modules (FIG. 5A) or one or more respective components and/ormodules of the server-side module 506. The client-side module 502provides client-side functionalities for the event monitoring and reviewprocessing and communications with the video server system 552. Thevideo server system 552 provides server-side functionalities for eventmonitoring and review processing for any number of client-side modules502 each residing on a respective client device 504. The video serversystem 556 also provides server-side functionalities for videoprocessing and camera control for any number of the video sources 522,including any number of control devices and the cameras 118.

In some implementations, the video server 554 includes one or moreprocessors 512, a video storage database 514, and device and accountdatabases 516. In some implementations, the video server system 552 alsoincludes a client interface server 556 and a camera interface server558. The client interface server 556 provides an I/O interface to one ormore client devices 504, and the camera interface server 558 provides anI/O interface to one or more video sources 520. The client interfaceserver 556 facilitates the client-facing input and output processing forthe video server system 552. For example, the client interface server556 generates web pages for reviewing and monitoring video captured bythe video sources 522 in a web browser application at a client 504. Insome implementations, the client interface server 556 or a transcodingproxy computer rescales (e.g., downscales) and/or changes the frame rateof video for transmission to a client 504. In some implementations, theclient interface server 504 also serves as the transcoding proxy. Thedatabases 516 store a plurality of profiles for reviewer accountsregistered with the video processing server, where a respective userprofile includes account credentials for a respective reviewer account,and one or more video sources linked to the respective reviewer account.The camera interface server 558 facilitates communications with one ormore video sources 522 (e.g., groups of one or more cameras 118 andassociated controller devices). The video storage database 514 storesraw video data received from the video sources 522, as well as varioustypes of metadata, such as motion events, event categories, eventcategory models, event filters, event masks, alert events, and camerahistories, for use in data processing for event monitoring and reviewfor each reviewer account.

In some implementations, the video server system 552 receivesinformation regarding alert events detected by other smart devices 204(e.g., hazards, sound, vibration, motion. In accordance with the alertevent information, the video server system 552 instructs one or morevideo sources 522 in the smart home environment 100 where the alertevent is detected to capture video and/or associate with the alert eventvideo, received from the video sources 522 in the same smart homeenvironment 100, that is contemporaneous or proximate in time with thealert event.

Examples of a representative client device 504 include, but are notlimited to, a handheld computer, a wearable computing device, a personaldigital assistant (PDA), a tablet computer, a laptop computer, a desktopcomputer, a cellular telephone, a smart phone, an enhanced generalpacket radio service (EGPRS) mobile phone, a media player, a navigationdevice, a game console, a television, a remote control, a point-of-sale(POS) terminal, vehicle-mounted computer, an ebook reader, or acombination of any two or more of these data processing devices or otherdata processing devices. For example, client devices 504-1, 504-2, and504-m are a smart phone, a tablet computer, and a laptop computer,respectively.

Examples of the one or more networks 162 include local area networks(LAN) and wide area networks (WAN) such as the Internet. The one or morenetworks 162 are, optionally, implemented using any known networkprotocol, including various wired or wireless protocols, such asEthernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution(LTE), Global System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), code division multiple access (CDMA), time divisionmultiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol(VoIP), Wi-MAX, or any other suitable communication protocol.

In some implementations, the video server system 552 is implemented onone or more standalone data processing apparatuses or a distributednetwork of computers. In some implementations, the video server 554, theclient interface server 556, and the camera interface server 558 areeach respectively implemented on one or more standalone data processingapparatuses or a distributed network of computers. In someimplementations, the video server system 552 also employs variousvirtual devices and/or services of third party service providers (e.g.,third-party cloud service providers) to provide the underlying computingresources and/or infrastructure resources of the video server system552. In some implementations, the video server system 552 includes, butis not limited to, a handheld computer, a tablet computer, a laptopcomputer, a desktop computer, or a combination of any two or more ofthese data processing devices or other data processing devices.

The server-client environment 550 shown in FIG. 5B includes both aclient-side portion (e.g., the client-side module 502) and a server-sideportion (e.g., the components and modules in the video server system552). The division of functionalities between the client and serverportions of operating environment 550 can vary in differentimplementations. Similarly, the division of functionalities between thevideo source 522 and the video server system 552 can vary in differentimplementations. For example, in some implementations, client-sidemodule 502 is a thin-client that provides only user-facing input andoutput processing functions, and delegates all other data processingfunctionalities to a backend server (e.g., the video server system 552).Similarly, in some implementations, a respective one of the videosources 522 is a simple video capturing device that continuouslycaptures and streams video data to the video server system 552 with noor limited local preliminary processing on the video data. Although manyaspects of the present technology are described from the perspective ofthe video server system 552, the corresponding actions performed by theclient device 504 and/or the video sources 522 would be apparent to onesskilled in the art without any creative efforts. Similarly, some aspectsof the present technology may be described from the perspective of theclient device or the video source, and the corresponding actionsperformed by the video server would be apparent to ones skilled in theart without any creative efforts. Furthermore, some aspects of thepresent technology may be performed by the video server system 552, theclient device 504, and the video sources 522 cooperatively.

It should be understood that operating environment 550 that involves thevideo server system 552, the video sources 522 and the video cameras 118is merely an example. Many aspects of operating environment 550 aregenerally applicable in other operating environments in which a serversystem provides data processing for monitoring and facilitating reviewof data captured by other types of electronic devices (e.g., smartthermostats 102, smart hazard detectors 104, smart doorbells 106, smartwall plugs 110, appliances 112 and the like).

The electronic devices, the client devices or the server systemcommunicate with each other using the one or more communication networks162. In an example smart home environment, two or more devices (e.g.,the network interface device 160, the hub device 180, and the clientdevices 504-m) are located in close proximity to each other, such thatthey could be communicatively coupled in the same sub-network 162A viawired connections, a WLAN or a Bluetooth Personal Area Network (PAN).The Bluetooth PAN is optionally established based on classical Bluetoothtechnology or Bluetooth Low Energy (BLE) technology. This smart homeenvironment further includes one or more other radio communicationnetworks 162B through which at least some of the electronic devices ofthe video sources 522-n exchange data with the hub device 180.Alternatively, in some situations, some of the electronic devices of thevideo sources 522-n communicate with the network interface device 160directly via the same sub-network 162A that couples devices 160, 180 and504-m. In some implementations (e.g., in the network 162C), both theclient device 504-m and the electronic devices of the video sources522-n communicate directly via the network(s) 162 without passing thenetwork interface device 160 or the hub device 180.

In some implementations, during normal operation, the network interfacedevice 160 and the hub device 180 communicate with each other to form anetwork gateway through which data are exchanged with the electronicdevice of the video sources 522-n. As explained above, the networkinterface device 160 and the hub device 180 optionally communicate witheach other via a sub-network 162A.

In some implementations, a video source 522 may be private (e.g., itscaptured videos and history are accessible only to the associateduser/account), public (e.g., its captured videos and history areaccessible by anyone), or shared (e.g., its captured videos and historyare accessible only to the associated user/account and other specificusers/accounts with whom the associated user has authorized access(e.g., by sharing with the other specific users)). Whether a videosource 522 is private, public, or shared is configurable by theassociated user.

In some implementations, the camera 118 also performs preliminary motiondetection on video captured by the camera 118. For example, the camera118 analyzes the captured video for significant changes in pixels. Whenmotion is detected by the preliminary motion detection, the camera 118transmits information to the hub device server system 508 or videoserver system 552 informing the server system of the preliminarydetected motion. The hub device server system 508 or video server system552, in accordance with the information of the detected motion, mayactivate sending of a motion detection notification to a client device504, log the preliminary detected motion as an alert event, and/orperform additional analysis of the captured video to confirm and/orclassify the preliminary detected motion.

FIG. 6 is a block diagram illustrating a representative hub device 180in accordance with some implementations. In some implementations, thehub device 180 includes one or more processing units (e.g., CPUs, ASICs,FPGAs, microprocessors, and the like) 602, one or more communicationinterfaces 604, memory 606, radios 640, and one or more communicationbuses 608 for interconnecting these components (sometimes called achipset). In some implementations, the hub device 180 includes one ormore input devices 610 such as one or more buttons for receiving input.In some implementations, the hub device 180 includes one or more outputdevices 612 such as one or more indicator lights, a sound card, aspeaker, a small display for displaying textual information and errorcodes, etc. Furthermore, in some implementations, the hub device 180uses a microphone and voice recognition or a camera and gesturerecognition to supplement or replace the keyboard. In someimplementations, the hub device 180 includes a location detection device614, such as a GPS (global positioning satellite) or other geo-locationreceiver, for determining the location of the hub device 180.

The hub device 180 optionally includes one or more built-in sensors (notshown), including, for example, one or more thermal radiation sensors,ambient temperature sensors, humidity sensors, IR sensors, occupancysensors (e.g., using RFID sensors), ambient light sensors, motiondetectors, accelerometers, and/or gyroscopes.

The radios 640 enables one or more radio communication networks in thesmart home environments, and allows a hub device to communicate withsmart devices. In some implementations, the radios 640 are capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) custom orstandard wired protocols (e.g., Ethernet, HomePlug, etc.), and/or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Communication interfaces 604 include, for example, hardware capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/orany of a variety of custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Memory 606 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 606, or alternatively the non-volatile memorywithin memory 606, includes a non-transitory computer readable storagemedium. In some implementations, memory 606, or the non-transitorycomputer readable storage medium of memory 606, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   Operating logic 616 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Hub device communication module 618 for connecting to and        communicating with other network devices (e.g., network        interface 160, such as a router that provides Internet        connectivity, networked storage devices, network routing        devices, server system 508, etc.) connected to one or more        networks 162 via one or more communication interfaces 604 (wired        or wireless);    -   Radio Communication Module 620 for connecting the hub device 180        to other devices (e.g., controller devices, smart devices 204 in        smart home environment 100, client devices 504) via one or more        radio communication devices (e.g., radios 640);    -   User interface module 622 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., smart devices 204 in smart home        environment 100) can be configured and/or viewed; and    -   Hub device database 624, including but not limited to:        -   Sensor information 6240 for storing and managing data            received, detected, and/or transmitted by one or more            sensors of the hub device 180 and/or one or more other            devices (e.g., smart devices 204 in smart home environment            100);        -   Device settings 6242 for storing operational settings for            one or more devices (e.g., coupled smart devices 204 in            smart home environment 100); and        -   Communication protocol information 6244 for storing and            managing protocol information for one or more protocols            (e.g., standard wireless protocols, such as ZigBee, Z-Wave,            etc., and/or custom or standard wired protocols, such as            Ethernet).

Each of the above identified elements (e.g., modules stored in memory206 of hub device 180) may be stored in one or more of the previouslymentioned memory devices (e.g., the memory of any of the smart devicesin smart home environment 100, FIG. 1), and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory606, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 606, optionally, stores additionalmodules and data structures not described above.

FIG. 7A is a block diagram illustrating the hub device server system 508in accordance with some implementations. The hub device server system508, typically, includes one or more processing units (CPUs) 702, one ormore network interfaces 704 (e.g., including an I/O interface to one ormore client devices and an I/O interface to one or more electronicdevices), memory 706, and one or more communication buses 708 forinterconnecting these components (sometimes called a chipset). Memory706 includes high-speed random access memory, such as DRAM, SRAM, DDRRAM, or other random access solid state memory devices; and, optionally,includes non-volatile memory, such as one or more magnetic disk storagedevices, one or more optical disk storage devices, one or more flashmemory devices, or one or more other non-volatile solid state storagedevices. Memory 706, optionally, includes one or more storage devicesremotely located from one or more processing units 702. Memory 706, oralternatively the non-volatile memory within memory 706, includes anon-transitory computer readable storage medium. In someimplementations, memory 706, or the non-transitory computer readablestorage medium of memory 706, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 710 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 712 for connecting the hub device        server system 508 to other systems and devices (e.g., client        devices, electronic devices, and systems connected to one or        more networks 162, FIGS. 1-5B) via one or more network        interfaces 704 (wired or wireless);    -   Server-side module 714, which provides server-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Data receiving module 7140 for receiving data from            electronic devices (e.g., video data from a camera 118,            FIG. 1) via the hub device 180, and preparing the received            data for further processing and storage in the data storage            database 7160;        -   Hub and device control module 7142 for generating and            sending server-initiated control commands to modify            operation modes of electronic devices (e.g., devices of a            smart home environment 100), and/or receiving (e.g., from            client devices 504) and forwarding user-initiated control            commands to modify operation modes of the electronic            devices;        -   Data processing module 7144 for processing the data provided            by the electronic devices, and/or preparing and sending            processed data to a device for review (e.g., client devices            504 for review by a user); and    -   Server database 716, including but not limited to:        -   Data storage database 7160 for storing data associated with            each electronic device (e.g., each camera) of each user            account, as well as data processing models, processed data            results, and other relevant metadata (e.g., names of data            results, location of electronic device, creation time,            duration, settings of the electronic device, etc.)            associated with the data, wherein (optionally) all or a            portion of the data and/or processing associated with the            hub device 180 or smart devices are stored securely;        -   Account database 7162 for storing account information for            user accounts, including user account information,            information and settings for linked hub devices and            electronic devices (e.g., hub device identifications), hub            device specific secrets, relevant user and hardware            characteristics (e.g., service tier, device model, storage            capacity, processing capabilities, etc.), user interface            settings, data review preferences, etc., where the            information for associated electronic devices includes, but            is not limited to, one or more device identifiers (e.g., MAC            address and UUID), device specific secrets, and displayed            titles; and        -   Device Information Database 7164 for storing device            information related to one or more hub devices, e.g., device            identifiers and hub device specific secrets, independently            of whether the corresponding hub devices have been            associated with any user account.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory706, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 706, optionally, stores additionalmodules and data structures not described above.

FIG. 7B is a block diagram illustrating the video server 554 inaccordance with some implementations. The video server 554, typically,includes one or more processing units (CPUs) 718, one or more networkinterfaces 720, memory 722, and one or more communication buses 724 forinterconnecting these components (sometimes called a chipset). Memory722 includes high-speed random access memory, such as DRAM, SRAM, DDRRAM, or other random access solid state memory devices; and, optionally,includes non-volatile memory, such as one or more magnetic disk storagedevices, one or more optical disk storage devices, one or more flashmemory devices, or one or more other non-volatile solid state storagedevices. Memory 722, optionally, includes one or more storage devicesremotely located from one or more processing units 718. Memory 722, oralternatively the non-volatile memory within memory 722, includes anon-transitory computer readable storage medium. In someimplementations, memory 722, or the non-transitory computer readablestorage medium of memory 722, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 726 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 728 for connecting the video server        554 to other systems and devices (e.g., client devices,        electronic devices, and systems connected to one or more        networks 162, FIGS. 1-5B) via one or more network interfaces 720        (wired or wireless);    -   Video server module 730, which provides server-side data        processing and functionalities for video and event monitoring        and review, including but not limited to:        -   Account administration module 7300 for creating reviewer            accounts, performing camera registration processing to            establish associations between video sources to their            respective reviewer accounts, and providing account            login-services to the client devices 504;        -   Video data receiving module 7302 for receiving raw video            data from the video sources 522, and preparing the received            video data for event processing and long-term storage in the            video storage database 514;        -   Camera control module 7304 for generating and sending            server-initiated control commands to modify the operation            modes of the video sources, and/or receiving and forwarding            user-initiated control commands to modify the operation            modes of the video sources 522;        -   Event detection module 7306 for detecting motion event            candidates in video streams from each of the video sources            522, including motion track identification, false positive            suppression, and event mask generation and caching;        -   Event categorization module 7308 for categorizing motion            events detected in received video streams;        -   Zone creation module 73010 for generating zones of interest            in accordance with user input;        -   Person identification module 73012 for identifying            characteristics associated with presence of humans in the            received video streams;        -   Filter application module 73014 for selecting event filters            (e.g., event categories, zones of interest, a human filter,            etc.) and applying the selected event filter to past and new            motion events detected in the video streams;        -   Zone monitoring module 73016 for monitoring motions within            selected zones of interest and generating notifications for            new motion events detected within the selected zones of            interest, where the zone monitoring takes into account            changes in surrounding context of the zones and is not            confined within the selected zones of interest;        -   Real-time motion event presentation module 73018 for            dynamically changing characteristics of event indicators            displayed in user interfaces as new event filters, such as            new event categories or new zones of interest, are created,            and for providing real-time notifications as new motion            events are detected in the video streams; and        -   Event post-processing module 3020 for providing summary            time-lapse for past motion events detected in video streams,            and providing event and category editing functions to user            for revising past event categorization results;        -   Alert events module 73022 for receiving information on alert            events (e.g., detected hazards, detected sounds, etc.),            instructing cameras 118 to capture video in accordance with            alert event information, and determining chronologies of            alert events; and        -   Camera events module 73024 for associating captured video            with alert events, from the same smart home environment 100,            that are proximate or contemporaneous in time, and logging            camera histories of camera events; and    -   Server database 732, including but not limited to:        -   Video storage database 7320 storing raw video data            associated with each of the video sources 522 (each            including one or more cameras 118) of each reviewer account,            as well as event categorization models (e.g., event            clusters, categorization criteria, etc.), event            categorization results (e.g., recognized event categories,            and assignment of past motion events to the recognized event            categories, representative events for each recognized event            category, etc.), event masks for past motion events, video            segments for each past motion event, preview video (e.g.,            sprites) of past motion events, and other relevant metadata            (e.g., names of event categories, location of the cameras            118, creation time, duration, etc.) associated with the            motion events;        -   Account database 7324 for storing account information for            user accounts, including user account information,            information and settings for linked hub devices and            electronic devices (e.g., hub device identifications), hub            device specific secrets, relevant user and hardware            characteristics (e.g., service tier, device model, storage            capacity, processing capabilities, etc.), user interface            settings, data review preferences, etc., where the            information for associated electronic devices includes, but            is not limited to, one or more device identifiers (e.g., MAC            address and UUID), device specific secrets, and displayed            titles;        -   Device Information Database 7326 for storing device            information related to one or more hub devices, e.g., device            identifiers and hub device specific secrets, independently            of whether the corresponding hub devices have been            associated with any user account; and        -   Camera events history 7328 for storing per-camera histories            of camera events, including alert events, chronologies of            alert events, and references to associated videos in the            video storage database 7320.

Video data stored in the video storage database 7320 includeshigh-quality versions 7321 and low-quality versions 7322 of videosassociated with each of the video sources 522. High-quality video 7321includes video in relatively high resolutions (e.g., 720P and/or 1080P)and relatively high frame rates (e.g., 24 frames per second).Low-quality video 7322 includes video in relatively low resolutions(e.g., 180P) and relatively low frame rates (e.g., 5 frames per second,10 frames per second).

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory722, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 722, optionally, stores additionalmodules and data structures not described above.

FIG. 7C is a block diagram illustrating the client interface server 556in accordance with some implementations. The client interface server556, typically, includes one or more processing units (CPUs) 734, one ormore network interfaces 736, memory 738, and one or more communicationbuses 740 for interconnecting these components (sometimes called achipset). Memory 738 includes high-speed random access memory, such asDRAM, SRAM, DDR RAM, or other random access solid state memory devices;and, optionally, includes non-volatile memory, such as one or moremagnetic disk storage devices, one or more optical disk storage devices,one or more flash memory devices, or one or more other non-volatilesolid state storage devices. Memory 738, optionally, includes one ormore storage devices remotely located from one or more processing units734. Memory 738, or alternatively the non-volatile memory within memory738, includes a non-transitory computer readable storage medium. In someimplementations, memory 738, or the non-transitory computer readablestorage medium of memory 738, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 742 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 744 for connecting the client        interface server 556 to other systems and devices (e.g., client        devices, video server 554, and systems connected to one or more        networks 162, FIGS. 1-5B) via one or more network interfaces 740        (wired or wireless);    -   Client interface module 746, which provides an I/O interface        between client devices 504 and the video server 554, including        but not limited to:        -   Video feed module 7462 for transmitting videos from the            video server system, or images extracted from same videos,            to client devices as video streams or periodically refreshed            images, and optionally transmitting particular views of            videos or images from videos;        -   Transcode module 7464 for rescaling (e.g., downscaling from            720P to 180P) video for transmission to client devices 504;        -   Client input module 7466 for receiving and processing input            commands from client devices (e.g., client device 504) 504            to change the video view being transmitted or controlling a            video source 522;        -   Camera view module 7468 for determining which views of            videos or images from videos are to be transmitted to client            devices; and        -   User interface module 74610 for generating user interfaces            (e.g., web pages), transmitted to client devices 504, for            viewing video feeds and corresponding event histories.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory738, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 738, optionally, stores additionalmodules and data structures not described above.

FIG. 7D is a block diagram illustrating the camera interface server 558in accordance with some implementations. The camera interface server558, typically, includes one or more processing units (CPUs) 748, one ormore network interfaces 750, memory 752, and one or more communicationbuses 754 for interconnecting these components (sometimes called achipset). Memory 752 includes high-speed random access memory, such asDRAM, SRAM, DDR RAM, or other random access solid state memory devices;and, optionally, includes non-volatile memory, such as one or moremagnetic disk storage devices, one or more optical disk storage devices,one or more flash memory devices, or one or more other non-volatilesolid state storage devices. Memory 752, optionally, includes one ormore storage devices remotely located from one or more processing units748. Memory 752, or alternatively the non-volatile memory within memory752, includes a non-transitory computer readable storage medium. In someimplementations, memory 752, or the non-transitory computer readablestorage medium of memory 752, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 756 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 758 for connecting the camera        interface server 558 to other systems and devices (e.g., client        devices, video server 554, and systems connected to one or more        networks 162, FIGS. 1-5B) via one or more network interfaces 754        (wired or wireless); and    -   Camera interface module 760 for providing an I/O interface        between video sources 522 and the video server 554.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory752, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 752, optionally, stores additionalmodules and data structures not described above.

In some implementations, at least some of the functions of the videoserver 554, client interface server 556, and camera interface server 558are performed by the hub device server system 508, and the correspondingmodules and sub-modules of these functions may be included in the hubdevice server system 508. In some implementations, at least some of thefunctions of the hub device server system 508 are performed by the videoserver 554, client interface server 556, and/or camera interface server558, and the corresponding modules and sub-modules of these functionsmay be included in the video server 554, client interface server 556,and/or camera interface server 558.

FIGS. 8A-8B are block diagrams illustrating a representative clientdevice 504 associated with a user (e.g., reviewer) account in accordancewith some implementations. The client device 504, typically, includesone or more processing units (CPUs) 802, one or more network interfaces804, memory 806, and one or more communication buses 808 forinterconnecting these components (sometimes called a chipset). Theclient device also includes a user interface 810 and one or morebuilt-in sensors 890 (e.g., accelerometer 892 and gyroscope 894). Userinterface 810 includes one or more output devices 812 that enablepresentation of media content, including one or more speakers and/or oneor more visual displays. User interface 810 also includes one or moreinput devices 814, including user interface components that facilitateuser input such as a keyboard, a mouse, a voice-command input unit ormicrophone, a touch screen display, a touch-sensitive input pad, agesture capturing camera, or other input buttons or controls.Furthermore, the client device 504 optionally uses a microphone andvoice recognition or a camera and gesture recognition to supplement orreplace the keyboard. Further, the client device 504 optionally uses theaccelerometer to detect changes in the orientation of the client device504, and in particular applications and contexts interpret the change inorientation detected by the accelerometer as user input. In someimplementations, the client device 504 includes one or more cameras,scanners, or photo sensor units for capturing images (not shown). Insome implementations, the client device 504 optionally includes alocation detection device 816, such as a GPS (global positioningsatellite) or other geo-location receiver, for determining the locationof the client device 504.

Memory 806 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 806, optionally, includes one or more storagedevices remotely located from one or more processing units 802. Memory806, or alternatively the non-volatile memory within memory 806,includes a non-transitory computer readable storage medium. In someimplementations, memory 806, or the non-transitory computer readablestorage medium of memory 806, stores the following programs, modules,and data structures, or a subset or superset thereof:

-   -   Operating system 818 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 820 for connecting the client        device 504 to other systems and devices (e.g., hub device server        system 508, video server system 552, video sources 522)        connected to one or more networks 162 via one or more network        interfaces 804 (wired or wireless);    -   Presentation module 821 for enabling presentation of information        (e.g., user interfaces for application(s) 824 and web browser        module 823 or the client-side module 502, widgets, websites and        web pages thereof, and/or games, audio and/or video content,        text, etc.) at the client device 504 via the one or more output        devices 812 (e.g., displays, speakers, etc.) associated with the        user interface 810;    -   Input processing module 822 for detecting one or more user        inputs or interactions from one of the one or more input devices        814 and optionally the accelerometer 892 and interpreting the        detected input or interaction;    -   Web browser module 823 for navigating, requesting (e.g., via        HTTP), and displaying websites and web pages thereof, including        a web interface for logging into a reviewer account, controlling        the video sources associated with the reviewer account,        establishing and selecting event filters, and editing and        reviewing motion events detected in the video streams of the        video sources;    -   One or more applications 824 for execution by the client device        504 (e.g., games, social network applications, smart home        applications, and/or other web or non-web based applications),        for controlling devices (e.g., sending commands, configuring        settings, etc. to hub devices and/or other client or electronic        devices), and for reviewing data captured by the devices (e.g.,        device status and settings, captured data, or other information        regarding the hub device or other connected devices);    -   User interface module 826 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., smart devices 204 in smart home        environment 100) can be configured and/or viewed;    -   Client-side module 502, which provides client-side data        processing and functionalities for device control, data        processing, data review, and monitoring and reviewing videos        from one or more video sources and camera events, including but        not limited to:        -   Hub device and device control module 8280 for generating            control commands for modifying an operating mode of the hub            device or the electronic devices in accordance with user            inputs; and        -   Data review module 8282 for providing user interfaces for            reviewing data processed by the hub device server system 508            or video server system 552;        -   Account registration module 8284 for establishing a reviewer            account and registering one or more video sources with the            hub device server system 508 or video server system 552;        -   Camera setup module 8286 for setting up one or more video            sources within a local area network, and enabling the one or            more video sources to access the hub device server system            508 or video server system 552 on the Internet through the            local area network;        -   Camera control module 8288 for generating control commands            for modifying an operating mode of the one or more video            sources in accordance with user input;        -   Event review interface module 82810 for providing user            interfaces for reviewing event timelines, camera histories            with camera events, editing event categorization results,            selecting event filters, presenting real-time filtered            motion events based on existing and newly created event            filters (e.g., event categories, zones of interest, a human            filter, etc.), presenting real-time notifications (e.g.,            pop-ups) for newly detected motion events, and presenting            smart time-lapse of selected motion events;        -   Zone creation module 82814 for providing a user interface            for creating zones of interest for each video stream in            accordance with user input, and sending the definitions of            the zones of interest to the hub device server system 508 or            video server system 552;        -   Notification module 82814 for generating real-time            notifications for all or selected alert events or motion            events on the client device 504 outside of the event review            user interface; and        -   Camera view module 82816 for generating control commands for            modifying a view of a video transmitted to the client device            504 in accordance with user input; and    -   Client data 830 storing data associated with the user account,        electronic devices, and video sources 522, including, but is not        limited to:        -   Account data 8300 storing information related to both user            accounts loaded on the client device 504 and electronic            devices (e.g., of the video sources 522) associated with the            user accounts, wherein such information includes cached            login credentials, hub device identifiers (e.g., MAC            addresses and UUIDs), electronic device identifiers (e.g.,            MAC addresses and UUIDs), user interface settings, display            preferences, authentication tokens and tags, password keys,            etc.;        -   Local data storage database 8302 for selectively storing raw            or processed data associated with electronic devices (e.g.,            of the video sources 522, such as a camera 118); and        -   Video data cache 8304 for caching video and image data from            video feeds;    -   Blurred image data 832; and    -   Blurring algorithms and parameters 834; for generating blurred        image data 832 from video/image data in video data cache 8304.

Video data cache 8304 includes cached video/image data for respectivecameras associated with a user of the client device 804. For example, asshown in FIG. 8B, the video data cache 8304 includes cached video/imagedata 8304-1 for a first camera, cached video/image data 8304-2 for asecond camera, up to cached video/image data 8304-p for a p-th camera.At a given moment, video data cache 8304 may not have cached video/imagedata for a given camera (e.g., due to the camera being newly associatedwith the user, due to the cache being cleared, due to the cachedvideo/image data being expired and removed from the cache).

Blurred image data 832 includes sets of progressively blurred images forrespective cameras. For example, as shown in FIG. 8B, the blurred imagedata 832 includes blurred image data (e.g., a set of progressivelyblurred images) 832-1 for the first camera, blurred image data 832-2 forthe second camera, up to blurred image data 832-p for the p-th camera.

In some implementations, the client device 504 caches camera history aswell as video data 8304. For example, whenever the client device 504receives camera events history 7328 data from the video server 554, themost recent camera events history (e.g., history from the past twohours, the most recent 20 events) is cached at the client device (e.g.,in client data 830). This cached history data may be accessed for quickdisplay of camera history information (e.g., in user interface 1304(FIG. 13A)).

In some implementations, the client-side module 502 and user interfacemodule 826 are parts, modules, or components of a particular application824 (e.g., a smart home management application).

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, modules or datastructures, and thus various subsets of these modules may be combined orotherwise re-arranged in various implementations. In someimplementations, memory 806, optionally, stores a subset of the modulesand data structures identified above. Furthermore, memory 806,optionally, stores additional modules and data structures not describedabove.

In some implementations, at least some of the functions of the hubdevice server system 508 or the video server system 552 are performed bythe client device 504, and the corresponding sub-modules of thesefunctions may be located within the client device 504 rather than thehub device server system 508 or video server system 552. In someimplementations, at least some of the functions of the client device 504are performed by the hub device server system 508 or video server system552, and the corresponding sub-modules of these functions may be locatedwithin the hub device server system 508 or video server system 552rather than the client device 504. The client device 504 and the hubdevice server system 508 or video server system 552 shown in FIGS. 7A-8,respectively, are merely illustrative, and different configurations ofthe modules for implementing the functions described herein are possiblein various implementations.

FIG. 9A is a block diagram illustrating a representative smart device204 in accordance with some implementations. In some implementations,the smart device 204 (e.g., any devices of a smart home environment 100,FIGS. 1 and 2) includes one or more processing units (e.g., CPUs, ASICs,FPGAs, microprocessors, and the like) 902, one or more communicationinterfaces 904, memory 906, radios 940, and one or more communicationbuses 908 for interconnecting these components (sometimes called achipset). In some implementations, user interface 910 includes one ormore output devices 912 that enable presentation of media content,including one or more speakers and/or one or more visual displays. Insome implementations, user interface 910 also includes one or more inputdevices 914, including user interface components that facilitate userinput such as a keyboard, a mouse, a voice-command input unit ormicrophone, a touch screen display, a touch-sensitive input pad, agesture capturing camera, or other input buttons or controls.Furthermore, some smart devices 204 use a microphone and voicerecognition or a camera and gesture recognition to supplement or replacethe keyboard. In some implementations, the smart device 204 includes oneor more image/video capture devices 918 (e.g., cameras, video cameras,scanners, photo sensor units). Optionally, the client device includes alocation detection device 916, such as a GPS (global positioningsatellite) or other geo-location receiver, for determining the locationof the smart device 204.

The built-in sensors 990 include, for example, one or more thermalradiation sensors, ambient temperature sensors, humidity sensors, IRsensors, occupancy sensors (e.g., using RFID sensors), ambient lightsensors, motion detectors, accelerometers, and/or gyroscopes.

The radios 940 enable one or more radio communication networks in thesmart home environments, and allow a smart device 204 to communicatewith other devices. In some implementations, the radios 940 are capableof data communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) custom orstandard wired protocols (e.g., Ethernet, HomePlug, etc.), and/or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Communication interfaces 904 include, for example, hardware capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/orany of a variety of custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Memory 906 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 906, or alternatively the non-volatile memorywithin memory 906, includes a non-transitory computer readable storagemedium. In some implementations, memory 906, or the non-transitorycomputer readable storage medium of memory 906, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   Operating logic 920 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Device communication module 922 for connecting to and        communicating with other network devices (e.g., network        interface 160, such as a router that provides Internet        connectivity, networked storage devices, network routing        devices, server system 508, etc.) connected to one or more        networks 162 via one or more communication interfaces 904 (wired        or wireless);    -   Radio Communication Module 924 for connecting the smart device        204 to other devices (e.g., controller devices, smart devices        204 in smart home environment 100, client devices 504) via one        or more radio communication devices (e.g., radios 940)    -   Input processing module 926 for detecting one or more user        inputs or interactions from the one or more input devices 914        and interpreting the detected inputs or interactions;    -   User interface module 928 for providing and displaying a user        interface in which settings, captured data, and/or other data        for one or more devices (e.g., the smart device 204, and/or        other devices in smart home environment 100) can be configured        and/or viewed;    -   One or more applications 930 for execution by the smart device        930 (e.g., games, social network applications, smart home        applications, and/or other web or non-web based applications)        for controlling devices (e.g., executing commands, sending        commands, and/or configuring settings of the smart device 204        and/or other client/electronic devices), and for reviewing data        captured by devices (e.g., device status and settings, captured        data, or other information regarding the smart device 204 and/or        other client/electronic devices);    -   Device-side module 932, which provides device-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Command receiving module 9320 for receiving, forwarding,            and/or executing instructions and control commands (e.g.,            from a client device 504, from a smart home provider server            system 164, from user inputs detected on the user interface            910, etc.) for operating the smart device 204;        -   Data processing module 9322 for processing data captured or            received by one or more inputs (e.g., input devices 914,            image/video capture devices 918, location detection device            916), sensors (e.g., built-in sensors 990), interfaces            (e.g., communication interfaces 904, radios 940), and/or            other components of the smart device 204, and for preparing            and sending processed data to a device for review (e.g.,            client devices 504 for review by a user); and    -   Device data 934 storing data associated with devices (e.g., the        smart device 204), including, but is not limited to:        -   Account data 9340 storing information related to user            accounts loaded on the smart device 204, wherein such            information includes cached login credentials, smart device            identifiers (e.g., MAC addresses and UUIDs), user interface            settings, display preferences, authentication tokens and            tags, password keys, etc.; and        -   Local data storage database 9342 for selectively storing raw            or processed data associated with the smart device 204            (e.g., video surveillance footage captured by a camera 118).

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory906, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 906, optionally, stores additionalmodules and data structures not described above.

FIG. 9B is a block diagram illustrating a representative camera 118 inaccordance with some implementations. In some implementations, thecamera 118 includes one or more processing units (e.g., CPUs, ASICs,FPGAs, microprocessors, and the like) 942, one or more communicationinterfaces 944, memory 946, and one or more communication buses 948 forinterconnecting these components (sometimes called a chipset). In someimplementations, the camera 118 includes one or more input devices 950such as one or more buttons for receiving input and one or moremicrophones. In some implementations, the camera 118 includes one ormore output devices 952 such as one or more indicator lights, a soundcard, a speaker, a small display for displaying textual information anderror codes, playing audio, etc. In some implementations, the camera 118optionally includes a location detection device 954, such as a GPS(global positioning satellite) or other geo-location receiver, fordetermining the location of the camera 118.

Communication interfaces 944 include, for example, hardware capable ofdata communications using any of a variety of custom or standardwireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread,Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/orany of a variety of custom or standard wired protocols (e.g., Ethernet,HomePlug, etc.), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Memory 946 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM, or other random access solid state memory devices; and,optionally, includes non-volatile memory, such as one or more magneticdisk storage devices, one or more optical disk storage devices, one ormore flash memory devices, or one or more other non-volatile solid statestorage devices. Memory 946, or alternatively the non-volatile memorywithin memory 946, includes a non-transitory computer readable storagemedium. In some implementations, memory 946, or the non-transitorycomputer readable storage medium of memory 946, stores the followingprograms, modules, and data structures, or a subset or superset thereof:

-   -   Operating system 956 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 958 for connecting the camera 118        to other computing devices (e.g., hub device server system 508,        video server system 552, the client device 504, network routing        devices, one or more controller devices, and networked storage        devices) connected to the one or more networks 162 via the one        or more communication interfaces 944 (wired or wireless);    -   Video control module 960 for modifying the operation mode (e.g.,        zoom level, resolution, frame rate, recording and playback        volume, lighting adjustment, AE and IR modes, etc.) of the        camera 118, enabling/disabling the audio and/or video recording        functions of the camera 118, changing the pan and tilt angles of        the camera 118, resetting the camera 118, and/or the like;    -   Video capturing module 964 for capturing and generating a video        stream and sending the video stream to the hub device server        system 508 or video server system 552 as a continuous feed or in        short bursts, and optionally generating a rescaled version of        the video stream and sending the video stream at the original        captured resolution and the rescaled resolution;    -   Video caching module 966 for storing some or all captured video        data locally at one or more local storage devices (e.g., memory,        flash drives, internal hard disks, portable disks, etc.);    -   Local video processing module 968 for performing preliminary        processing of the captured video data locally at the camera 118,        including for example, compressing and encrypting the captured        video data for network transmission, preliminary motion event        detection, preliminary false positive suppression for motion        event detection, preliminary motion vector generation, etc.; and    -   Camera data 970 storing data, including but not limited to:        -   Camera settings 972, including network settings, camera            operation settings, camera storage settings, etc.; and        -   Video data 974, including video segments and motion vectors            for detected motion event candidates to be sent to the hub            device server system 508 or video server system 552.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory946, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 946, optionally, stores additionalmodules and data structures not described above. Additionally, camera118, being an example of a smart device 204, optionally includescomponents and modules included in smart device 204 as shown in FIG. 9Athat are not shown in FIG. 9B.

FIG. 10 is a block diagram illustrating the smart home provider serversystem 164 in accordance with some implementations. The smart homeprovider server system 164, typically, includes one or more processingunits (CPUs) 1002, one or more network interfaces 1004 (e.g., includingan I/O interface to one or more client devices and an I/O interface toone or more electronic devices), memory 1006, and one or morecommunication buses 1008 for interconnecting these components (sometimescalled a chipset). Memory 1006 includes high-speed random access memory,such as DRAM, SRAM, DDR RAM, or other random access solid state memorydevices; and, optionally, includes non-volatile memory, such as one ormore magnetic disk storage devices, one or more optical disk storagedevices, one or more flash memory devices, or one or more othernon-volatile solid state storage devices. Memory 1006, optionally,includes one or more storage devices remotely located from one or moreprocessing units 1002. Memory 1006, or alternatively the non-volatilememory within memory 1006, includes a non-transitory computer readablestorage medium. In some implementations, memory 1006, or thenon-transitory computer readable storage medium of memory 1006, storesthe following programs, modules, and data structures, or a subset orsuperset thereof:

-   -   Operating system 1010 including procedures for handling various        basic system services and for performing hardware dependent        tasks;    -   Network communication module 1012 for connecting the smart home        provider server system 164 to other systems and devices (e.g.,        client devices, electronic devices, hub device server system        508, video server system 552, and systems connected to one or        more networks 162, FIGS. 1-5B) via one or more network        interfaces 1004 (wired or wireless);    -   Server-side module 1014, which provides server-side        functionalities for device control, data processing and data        review, including but not limited to:        -   Data receiving module 10140 for receiving data from            electronic devices (e.g., video data from a camera 118, FIG.            1), and preparing the received data for further processing            and storage in the data storage database 10160;        -   Device control module 10142 for generating and sending            server-initiated control commands to modify operation modes            of electronic devices (e.g., devices of a smart home            environment 100), and/or receiving (e.g., from client            devices 504) and forwarding user-initiated control commands            to modify operation modes of the electronic devices;        -   Data processing module 10144 for processing the data            provided by the electronic devices, and/or preparing and            sending processed data to a device for review (e.g., client            devices 504 for review by a user); and    -   Server database 1016, including but not limited to:        -   Data storage database 10160 for storing data associated with            each electronic device (e.g., each camera) of each user            account, as well as data processing models, processed data            results, and other relevant metadata (e.g., names of data            results, location of electronic device, creation time,            duration, settings of the electronic device, etc.)            associated with the data, wherein (optionally) all or a            portion of the data and/or processing associated with the            electronic devices are stored securely; and        -   Account database 10162 for storing account information for            user accounts, including user account information,            information and settings for linked hub devices and            electronic devices (e.g., hub device identifications), hub            device specific secrets, relevant user and hardware            characteristics (e.g., service tier, device model, storage            capacity, processing capabilities, etc.), user interface            settings, data review preferences, etc., where the            information for associated electronic devices includes, but            is not limited to, one or more device identifiers (e.g., MAC            address and UUID), device specific secrets, and displayed            titles.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures, or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various implementations. In some implementations, memory1006, optionally, stores a subset of the modules and data structuresidentified above. Furthermore, memory 1006, optionally, storesadditional modules and data structures not described above.

Furthermore, in some implementations, the functions of any of thedevices and systems described herein (e.g., hub device 180, hub deviceserver system 508, video server system 552, client device 504, smartdevice 204, camera 118, smart home provider server system 164) areinterchangeable with one another and may be performed by any otherdevices or systems, where the corresponding sub-modules of thesefunctions may additionally and/or alternatively be located within andexecuted by any of the devices and systems. As one example, generatingof user interfaces may be performed by the user interface module 74610(which may be located at the client interface server 556 or at the videoserver 554) or by the user interface module 826, depending on whetherthe user is accessing the video feeds and corresponding historiesthrough a web browser 823 or an application 824 (e.g., a dedicated smarthome management application) at the client device 504. The devices andsystems shown in and described with respect to FIGS. 6-10 are merelyillustrative, and different configurations of the modules forimplementing the functions described herein are possible in variousimplementations.

Exemplary User Interfaces

FIGS. 11A-11V illustrate example user interfaces on a client device formonitoring and reviewing video feeds in accordance with someimplementations. FIG. 11A illustrates a client device 504 (e.g., amobile device, such as a smart phone) with a touch screen 1102 andoptionally an accelerometer 892 and/or a gyroscope 894 (FIG. 8A). A userinterface 1104 of an application 824 is displayed on the touch screen1102. In some implementations, the application is a dedicated smart homemanagement application (also referred to below as a “smart homeapplication”), and the user interface 1104 is a home page or screen ofthe smart home management application. The user interface 1104 includesmultiple user interface objects (e.g., buttons, icons, etc.) thatdisplay information associated with a smart home environment 100associated with the user and/or serve as affordances with which a usermay interact to access functionalities associated with the smart homeapplication. For example, the user interface 1104 includes a menu object1106, a settings object 1108, a mode icon 1109 and corresponding label1110, one or more thermostat objects 1112, a “Protect” object 1114, andone or more camera objects 1116 with respective corresponding labels1118.

The menu and settings objects 1106 and 1108, when activated by the user,provides access to an options menu or interface and a settings menu orinterface for the smart home application, respectively. In someimplementations, the menu object 1106 is displayed as a 3-line“hamburger menu” icon (e.g., as shown in FIG. 11A), and the settingsicon is displayed as a gear icon (e.g., as shown in FIG. 11A). The modeicon 1109 and label 1110 indicates the operating mode of the smart homeenvironment 100 with which the information displayed in user interface1104 is associated (e.g., the user's home). For example, the smart homeenvironment 100 may operate in a “Home” mode and an “Away” mode. In the“Home” mode, the user is presumed to be in the smart home environment100 (e.g., within the structure 150). In the “Away” mode, the user ispresumed to be remote from the smart home environment 100. Smart devices204 may operate differently in the “Home” mode than in the “Away” mode,and certain notifications of events may be elided when in “Home” mode.The user may access a menu to change the mode by activating the modeicon 1109 (e.g., by tapping on the mode icon 1109 with a single tapgesture).

Thermostat objects 1112-A and 1112-B correspond to respective smartthermostats 102 in the smart home environment 100 and display thecurrent detected temperatures and/or the set temperatures at thecorresponding smart thermostats 102. “Protect” object 1114 providesaccess to a history of alert events (e.g., detected hazards, detectedsounds, detected vibrations, operation of smart door lock 120, etc.)associated with the smart home environment 100. The user accesses the“Protect” history by activating the “Protect” object 1114 (e.g., bytapping on the “Protect” object 1114 on the touch screen 1102).

The camera objects 1116-A, 1116-B, and 1116-C correspond to respectivevideo sources 522 (or, more particularly, respective cameras 118) withinthe smart home environment 100. The labels 1118-A, 1118-B, and 1118-Cindicate the respective video sources 522 to which the respective cameraobjects 1116 correspond. For example, the camera object 1116-Acorresponds to a camera 118 labeled “Outside” 1118-A.

Within a respective camera object 1116, a view of a video feed or streamfrom the corresponding camera is displayed. For example, a view 1120 ofthe video feed from the “Outside” 1118-A camera is displayed in cameraobject 1116-A, a view 1122 of the video feed from the “Front door”1118-B camera is displayed in camera object 1116-B, and a view 1124 ofthe video feed from the “Dining room” 1118-C camera is displayed incamera object 1116-C. In some implementations, the view of a video feedis displayed in a camera object 1116 as a real-time (or near real-time),live video stream from the corresponding camera or as periodicallyrefreshed (e.g., at a rate less than typical frame rates for video)still images. In some implementations, the view is displayed at aresolution different from the original resolution and/or frame rate inwhich the video was captured. For example, the video views displayed inthe camera objects 1116 are displayed at an 180P (180 horizontal linesprogressive scan) resolution and at a frame rate of 5 or 10 frames persecond, which is different from the original capture resolution (e.g.,720P or 1080P) and the original frame rate.

In some implementations, the view displayed in a camera object 1116 iscropped from the original video to fit the size and shape of the cameraobject 1116, and the cropping is positioned to focus on a particularportion of the video for display. For example, view 1120 is cropped toview 1120-1 to fit into circle-shaped object 1116-A, view 1122 iscropped to view 1122-1 to fit into circle-shaped object 1116-B, and view1124 is cropped to view 1124-1 to fit into circle-shaped object 1116-C.The cropping and focus is further illustrated in FIG. 11B. FIG. 11Billustrates the camera objects 1116 and the frame widths and heights,scaled relative to the camera objects 1116, of the videos from thecorresponding to cameras 118 corresponding to the camera objects 1116.As shown, frame 1117-A, corresponding to the video from the “Outside”1118-A camera, is relatively larger than camera object 1116-A; frame1117-B, corresponding to the video from the “Front door” 1118-B camera,is relatively larger than camera object 1116-B; and frame 1117-C,corresponding to the video from the “Dining room” 1118-C camera, isrelatively larger than camera object 1116-C. Frame 1117-A is cropped toview 1120-1 for display in 1116-A. Frame 1117-B is cropped to view1122-1 for display in 1116-B. Frame 1117-C is cropped to view 1120-3 fordisplay in 1116-C. The cropping may be adjusted by the smart homeapplication (e.g., the camera view module 82816) or by the hub deviceserver system 508 or video server system 552 to a different positionalong the span of the video frame, which puts a different portion of theframe into display. In some implementations, the video frame 1117 iszoomed so that the height of the zoomed frame 1117 matches the height ofthe object 1116, and the object 1116 is centered relative to the frame1117 (i.e., the cropping is centered to display the center portion ofthe frame 1117).

It should be appreciated that while the camera objects 1116 are shown ascircular in the drawings, the camera objects 1116 may be in other shapes(e.g., square, rectangle, etc.) or each camera object 1116 may have adistinct shape (e.g., one camera object 1116 has a circular shape,another camera object 1116 has a square shape, and so on).

Additionally, as shown in FIG. 11B, views 1120, 1122, and 1124 do notinclude the entirety of the respective frames, but respective portionsthereof. For example, view 1120-1 includes an upper portion of the frame1117-A. As will be described below, the user may change the view toinclude a different portion of the corresponding frame. In some otherimplementations, a video feed is displayed without cropping in a cameraobject 1116; the camera object is shaped and sized accordingly.

Continuing in FIG. 11C, a user may adjust the views 1120, 1122, and 1124displayed in the camera objects 1116 by performing a user input, such asa gesture on the touch screen 1102 (e.g., a swipe gesture 1128 withcontact (e.g., finger contact) 1126 across the touch screen 1102 justbelow the camera objects 1116) or a change in the orientation of theclient device 504 (e.g., rotating 1129 the client device 504 about avertical axis). In response to the gesture 1128 with contact 1126 or tothe orientation change 1129, the views 1120, 1122, and 1124 in cameraobjects 1116 change to views 1120-2, 1122-2, and 1124-2, respectively,as shown in FIG. 11D. In some implementations, changing the viewincludes shifting the cropped area(s) displayed in the camera object(s)1116 to different portion(s) of the corresponding frame(s); the viewchange pans the cropped area to another portion of the frame. Forexample, view 1120-1 showed three cacti from the frame 1117-A. With theview change, the view 1120 has shifted left relative to frame 1117-A tobecome view 1120-2, which shows just two cacti. It should be appreciatedthat, while FIGS. 11C-11D show a horizontal view change in response to ahorizontal gesture or horizontal orientation change, vertical and/ordiagonal view changes in response to other particular gestures ororientation changes are possible.

In some implementations, after the view change in response to thegesture or orientation change, the views stay in their post-changestates (i.e., as 1120-2, 1122-2, and 1124-2, respectively) even when theuser input triggering the change is terminated (e.g., the contact 1126is no longer detected on the touch screen 1102, the orientation ofclient device 504 stops changing) (e.g., as shown in FIG. 11E). In someimplementations, the user may perform an input (e.g., shaking the clientdevice 504 (detected by the accelerometer 892), a predefined gesture(e.g., double tap or a tap and hold in an area in user interface 1104near and away from the camera objects 1116), a voice command) to forcethe smart home application to reset the changed views back to views1120-1, 1122-1, and 1124-1. In some implementations, the user mayperform an input (e.g., single tap gesture, a voice command) on a cameraobject 1116 to selectively reset the view displayed in that cameraobject 1116 back to the pre-change state, while the remainder of theviews remain in their post-change states.

In some other implementations, after the view change in response to thegesture or orientation change, the views 1120, 1122, and 1124automatically return or reset to their pre-change states (i.e., returnto 1120-1, 1122-1, and 1124-1, respectively) even when the user inputtriggering the change is terminated (e.g., the contact 1126 is no longerdetected on the touch screen 1102, the orientation of client device 504stops changing). For example, the views 1120, 1122, and 1124automatically return to views 1120-1, 1122-1, and 1124-1, respectively,after a delay (e.g., 3 seconds) after the contact 1126 is lifted off thetouch screen 1102 to complete the gesture 1128. In some implementations,to prevent the automatic return to the pre-change views, the user mayperform another user input during the delay period (e.g., a single tapgesture with contact 1127 near where contact 1126 was last detected). Inaccordance with the another user input, the views 1120-2, 1122-2, and1124-2 are maintained. In some implementations, the user may perform aninput (e.g., single tap gesture, a voice command) on a camera object1116 to selectively maintain the view displayed in that camera object1116 in the post-change state, while the remainder of the views returnor reset to their pre-change states.

Continuing in FIG. 11E, a user may change the data usage of the views1120, 1122, and 1124 displayed in the camera objects 1116. In FIG. 11E,a gesture 1132 on the touch screen 1102 (e.g., a swipe gesture 1132 withcontact 1130 across the touch screen 1102 over the camera objects 1116).In response to the gesture 1132, the smart home application displaysuser interface objects (e.g., button, icon, etc.) 1134 and 1136 in theuser interface 1104. User interface object 1134 is an affordancecorresponding to a live stream mode, and user interface object 1136 isan affordance corresponding to a data save mode. In live stream mode,the views 1120, 1122, and 1124 are displayed in the camera objects 1116as live video streams. In data save mode, the views 1120, 1122, and 1124are displayed in the camera objects 1116 as still images (e.g., framesextracted from the corresponding videos) refreshing periodically atrates less than the refresh rate or frame rate for the live stream video(e.g., if refresh/frame rate in live stream mode is 5 or 10 frames persecond, the refresh/frame rate in data save mode may be, for example, 1frame per second, 1 frame per two seconds, or 1 frame per 30 seconds).As shown in FIG. 11F, the live stream mode is active, as indicated bythe user interface object 1134 with “Live stream” in bold. In someimplementations, a user interface object corresponding to a toggleaffordance for toggling between live stream mode and data save mode isdisplayed in lieu of displaying a user interface object for each mode.

While the user interface objects 1134 and 1136 are displayed, the usermay select the user interface object corresponding to the non-activemode to change the views 1120, 1122, and 1124 to that mode. For example,in FIG. 11F, a gesture (e.g., a tap gesture with contact 1138) isdetected on user interface object 1136 corresponding to the data savemode. In response to the selection of the user interface object 1136,the views 1120, 1122, and 1124 are displayed in camera objects 1116 indata save mode, i.e., as periodically refreshed images. In someimplementations, when a view is displayed in data save mode, a timericon 1140 is displayed near the corresponding label to indicate that theview is in data save mode and also indicate a time until the next imagerefresh. For example, a timer icon 1140 is displayed next to the“Outside” 1118-A label corresponding to view 1120, as shown in FIG. 11G,indicating that the view 1120 is displayed as periodically refreshedimages. Similarly, as shown in FIG. 11G, a timer icon 1140 is displayednext to the “Front door” 1118-B label corresponding to view 1122 andnext to the “Dining room” 1118-C label corresponding to view 1124,indicating that views 1122 and 1124 are displayed in data save mode.

The user may want to adjust the view(s) displayed in particular cameraobjects 1116, rather than adjusting all of the views. In someimplementations, the smart home application facilitates selection ofparticular camera objects 1116 by the user. FIG. 11H illustrates aselection input (e.g., a single tap gesture with contact 1142) detectedon object 1116-A. In response to the selection gesture, camera object1116-A is selected, as illustrated in FIG. 11I by the thick borderaround camera object 1116-A.

Multiple camera objects 1116 may be selected, as shown in FIGS. 11I-11J.After camera object 1116-A is selected, a selection input (e.g., asingle tap gesture with contact 1144) is detected on camera object1116-B. In response to that selection gesture, camera object 1116-B isselected and camera object 1116-A remains selected, as illustrated inFIG. 11J.

After one or more camera objects 1116 are selected, a user input toadjust the views in the selected camera objects 1116 may be performed.For example, a swipe gesture (e.g., swipe gesture 1148 just below thecamera objects 1116 with contact 1146) or a change 1149 in theorientation of the client device 504 may be detected. In response to theuser input, the views 1120-1 and 1122-1 in camera objects 1116-A and1116-B, respectively, are changed to views 1120-2 and 1122-2,respectively. View 1124-1, displayed in the not-selected camera object1116-C, is maintained.

In some implementations, after the view change in response to thegesture or orientation change, the selected camera objects 1116 aredeselected and the changed views stay in their post-change states (i.e.,as 1120-2 and 1122-2, respectively) even when the user input triggeringthe change is terminated (e.g., the contact 1146 is no longer detectedon the touch screen 1102, the orientation of client device 504 stopschanging). In some implementations, the user may perform an input (e.g.,shaking the client device 504 (detected by the accelerometer 892), apredefined gesture (e.g., double tap or a tap and hold in an area inuser interface 1104 near and away from the camera objects 1116), a voicecommand) to force the smart home application to reset the changed viewsback to views 1120-1 and 1122-1. In some implementations, the user mayperform an input (e.g., single tap gesture, a voice command) on a cameraobject 1116 to selectively reset the changed view displayed in thatcamera object 1116 back to the pre-change state, while the remainder ofthe changed views remain in their post-change states.

In some other implementations, after the view change in response to thegesture or orientation change, the selected camera objects 1116 aredeselected and the views 1120 and 1122 automatically return or reset totheir pre-change states (i.e., return to 1120-1 and 1122-1,respectively) even when the user input triggering the change isterminated (e.g., the contact 1146 is no longer detected on the touchscreen 1102, the orientation of client device 504 stops changing). Forexample, the views 1120 and 1122 automatically return to views 1120-1and 1122-1, respectively, after a delay (e.g., 3 seconds) after thecontact 1146 is lifted off the touch screen 1102 to complete the gesture1148. In some implementations, to prevent the automatic return to thepre-change views for particular ones of the selected camera objects1116, the user may perform one or more user inputs during the delayperiod on the camera object(s) 1116 with the views the user wishes tomaintain in the post-change state. For example, in FIG. 11L, a singletap gesture is detected on camera object 1116-B with contact 1150. Inaccordance with one or more user inputs during the delay period, theselected camera objects 1116 are deselected, the view 1122-2 ismaintained, and the view 1120-2 resets to view 1122-1, as shown in FIG.11M.

While one or more of the camera objects 1116 are selected, the displaymode of the views in the selected camera objects 1116 may be changed.FIG. 11N shows camera objects 1116-A and 1116-B selected. A gesture(e.g., a swipe gesture 1152 over the camera objects 1116 with contact1151) is detected on the touch screen 1102. In response to the gesture1152, the smart home application displays user interface objects (e.g.,button, icon, etc.) 1134 and 1136 in the user interface 1104. As shownin FIG. 11O, live stream mode is active, as indicated by the userinterface object 1134 with “Live stream” in bold; the views displayed inselected camera objects 1116-A and 1116-B are displayed in live streammode.

While the user interface objects 1134 and 1136 are displayed, the usermay select the user interface object corresponding to the non-activemode to change the views displayed in the selected camera objects 1116-Aand 1116-B to that mode. For example, in FIG. 11O, a gesture (e.g., atap gesture with contact 1158) is detected on user interface object 1136corresponding to the data save mode. In response to the selection of theuser interface object 1136, the views 1120 and 1122 are displayed incamera objects 1116-A and 1116-B, respectively, in data save mode, i.e.,as periodically refreshed images. A timer icon 1140 is displayed next tothe “Outside” 1118-A label corresponding to view 1120 and next to the“Front door” label 1118-B corresponding to view 1122, as shown in FIG.11P, indicating that the views 1120 and 1122 are displayed asperiodically refreshed images.

In some implementations, a user may freeze a video feed displayed in acamera object 1116. FIG. 11Q illustrates a freeze gesture (e.g., atouch-and-hold gesture with contact 1160) detected on camera object1116-B. In response to the freeze gesture, the view 1122 is frozen orlocked to a frozen view 1122-3 corresponding to a frame of thecorresponding video; view 1122 stops streaming or refreshing. A lockicon 1162 is displayed next to the “Front door” 1118-B labelcorresponding to the camera object 1116-B, indicating that the view 1122is frozen, as shown in FIG. 11R. To end the view freezing, the user canperform a tap-and-hold gesture on the camera object 1116-B (i.e.,repeating the gesture shown in FIG. 11Q).

Each of the camera objects 1116 are associated with a respective cameraand its corresponding video feed. A user may perform a gesture on one ofthe camera objects 1116 to access a user interface that shows the videocorresponding to that camera object uncropped. For example, in FIG. 11Sa single tap gesture is detected on the camera object 1116-C with thecontact 1164. In response to the gesture, user interface 1166 isdisplayed on the touch screen 1102, replacing user interface 1104, asshown in FIG. 11T. User interface 1166 includes a camera name 1168(e.g., indicating the camera 118 for which a video feed is shown in theinterface 1166), backtracking affordance 1170 to backtrack to a previoususer interface (e.g., back to user interface 1104), settings affordance1172, a live video indicator 1174, camera on/off switch 1178, and videoregion 1180. Within the video region 1180, the video feed from the“Dining room” 1118-C camera corresponding to the tapped-upon cameraobject 1116-C is displayed without cropping and at a higher resolutionand/or higher frame rate than the resolution the video is displayed atwithin the camera object 1116-C (e.g., at the original captureresolution of 720P or 1080P at 24 frames per second rather than the 180Pat 5 or 10 frames per second used for display in the camera object1116-C).

The user interface 1166 also includes various controls, such as previousclip affordance 1182-A for skipping to a chronologically preceding videoclip captured by the “Dining room” 1118-C camera, rewind affordance1182-B for rewinding back in the video shown in the video region 1180,fast forward affordance 1182-C for fast forwarding in the video shown inthe video region 1180, next clip affordance 1182-D for skipping to achronologically succeeding video clip captured by the “Dining room”1118-C camera, and live affordance 1182-E for jumping directly to thelive video stream from the captured by the “Dining room” 1118-C camera.The user interface 1166 also includes a talk affordance 1184 forinitiating voice functionality that includes voice input from the userthat will be output by the “Dining room” 1118-C camera, an enhanceaffordance 1186 for initiating enhancement of the video displayed in thevideo region 1180, a quality indicator/affordance 1188 for switching ortoggling the video quality (e.g., resolution and/or frame rate) of thevideo displayed in the video region 1180, and history affordance 1190for accessing a history of camera events for the “Dining room” 1118-Ccamera. In response to a gesture on the history affordance (e.g., asingle tap gesture on history affordance 1190 with contact 1192), acamera history user interface 1304 (FIG. 13A) is displayed. Furtherdetails regarding the camera history user interface 1304 are describedbelow in relation to FIGS. 13A-13M.

In some implementations, the views in the camera objects 1116 aredisplayed with blurring transitions. For example, when the smart homeapplication is opened, the views in the camera objects 1116 are shownwith a blurring transition, as shown in FIG. 11U. The views 1120, 1122,and 1124 gradually “de-blur” or “un-blur.” For example, blurred viewsbecome progressively less blurry (the blurred views that are shown inFIG. 11U being one stage in the progressive de-blurring) toward theviews shown in FIG. 11A. Additionally, when a camera corresponding to acamera object 1116 goes offline (e.g., that camera lost its Wi-Ficonnection), the view for that camera may progressively blur to a blurryimage, and then black out.

In some implementations, the blurring/de-blurring includes displaying aset of progressively blurred images (e.g., 16 or 24 blurred images) fromcached video/image data 8304 for the pertinent camera, and displayingthese images sequentially. For example, when the smart home applicationis opened and a camera is connected, a de-blurring transition from ablurred view 11100 to an unblurred view 11102 involves starting from ablurred cached image from the camera and then displaying, in sequence,progressively less blurry images in the set of blurred images.Meanwhile, as the blurred images are displayed in sequence, the clientdevice 504 receives the video feed from the camera and inserts imagesfrom the video feed under (e.g., in a lower z-layer) the blurred image.After the last blurred image is displayed, the blurred image is removed,revealing the updated images from the video feed. The set ofprogressively blurred images are generated from cached video/image data8304 for the camera (in some implementations, the smart home applicationcaches the most recent (e.g., in the last hour) video/image data fromeach associated camera at the client device 504 as cached video/imagedata 8304) using well-known blurring techniques (e.g., Gaussian blur,bokeh). For example, as shown in FIG. 11V, a set of n (e.g., 16, 24)blurred images 1198 is generated using Gaussian blur techniques. Eachblurred image 1198 is blurred at a respective blur radius r_(n). As nincreases, r_(n) decreases. To “de-blur,” images 1198-1 thru 1198-n aredisplayed in sequence in order of decreasing blur radius, and then image1198-n is removed, revealing updated image 1199 from the video feed. Toblur, the set of blurred images are displayed in order of increasingblur radius. If cached video/image data 8304 is not available, a defaultimage (e.g., an image of a shutter) is displayed in the camera objectand then removed to reveal updated image 1199 from the video feed.

In some implementations, one or more of the views displayed within thecamera objects 1116 may be zoomed in or out. The zooming in or outincludes zooming in or out the frames of the video feed from which theview is derived, and cropping the zoomed in/out frames if needed, thusderiving the zoomed in/out view. A view may be zoomed out to fit thevideo frames entirely within the camera object 1116 without cropping, orzoomed in to further focus on a particular portion of the frames.

In some implementations, the sizes of the camera objects 1116 arestatic; the camera objects 1116 have a fixed size. In some otherimplementations, the camera objects 1116 have sizes that may change. Forexample, the hub device server system 508 or video server system 552analyzes the video feeds from the cameras 118 to detect motion activityoccurring in the video feeds. The camera object 1116 corresponding tothe video feed with the most detected activity (e.g., currently detectedactivity, historically detected activity over predefined period of time(e.g., within the last hour, within the last 12 hours, within the last24 hours, etc.)) is displayed at a larger size than the other cameraobjects 1116. In some implementations, the sizes of camera objects 1116are individually configurable by the user (e.g., in a settings interfaceaccessible from the settings affordance 1108). For example, the user canconfigure the camera objects 1116 corresponding to cameras 118 whosevideo feeds he wishes to give more attention to be larger. In someimplementations, the size of a camera object 1116 is automaticallyconfigured by the smart home application based on, for example, how manytimes the user has accessed the video feed corresponding to the cameraobject 1116 (e.g., by tapping on the camera object 1116 and opening theinterface 1166 for the corresponding video feed, as in FIGS. 11S-11T) orif a new alert event has been detected for the corresponding camera118). For example, a camera object 1116 may be enlarged when an alertevent associated with the corresponding camera 1118 has been detected,and the camera object 1116 remains enlarged until the user views thevideo associated with the alert event or after a predefined amount oftime elapsing after the alert event detection.

In some implementations, the user interfaces illustrated in FIGS.11A-11U, or variations thereof, may be displayed on other devices (e.g.,on a smart home application running on a tablet computer) andapplications (e.g., in a web browser running on a desktop or laptopcomputer).

FIGS. 12A-12E illustrate example user interfaces on a client device formonitoring and reviewing a video feed in accordance with someimplementations. FIG. 12A illustrates a client device 504 (e.g., adesktop computer, a laptop computer) with a display 1202. A userinterface 1204 rendered in a web browser 823 is displayed on the display1202. In some implementations, the user interface 1204 is a web pageassociated with a smart home environment 100, and particularly, with acamera 118 in the smart home environment 100. The user interface 1204includes multiple user interface objects (e.g., buttons, icons, etc.)that display information associated with the associated camera 118and/or serve as affordances with which a user may interact to accessfunctionalities associated with the associated camera 118. The userinterface 1204 includes a video region 1206 in which a video feed 1207(e.g., a live video stream, a saved video clip) from the associatedcamera is displayed. A camera label 1290 and time indicator 1205identifies the associated camera 118 (in this case, the “Outside” 1118-A(FIG. 11A) camera) as well as the timestamp on the video feed 1207displayed in the video region 1206.

FIG. 12A illustrates the client device 504 displaying video controls foraccessing various functionalities related to the video feed 1207displayed in the video region 1206 and the associated camera. In FIG.12A, the video region 1206 of the user interface 1204 includes: anelevator bar with a handle 1210 for adjusting the zoom magnification ofthe video feed 1207 displayed in the video region 1206, affordance 1212for reducing the zoom magnification of the video feed 1207, andaffordance 1211 for increasing the zoom magnification of the video feed1207. In FIG. 12A, the video region 1206 of the user interface 1204 alsoincludes: affordance 1214 for enabling/disabling the microphone of theassociated camera; affordance 1216 for rewinding the video feed 1207 by10 seconds; affordance 1218 for pausing the video feed 1207; affordance1220 for forwarding the video feed 1207 by 10 seconds; affordance 122for jumping the video feed 1207 to the live video stream for theassociated camera; optionally affordance 1224 for adjusting the playbackquality of the video feed 1207; affordance 1226 for adjusting theplayback volume of the video feed 1207, including muting the playbackvolume; and affordance 1228 for displaying the video feed 1207 in fullscreen mode (e.g., the video region 1206 expanded to fit the width ofthe display 1202). The user interface 1204 also includes backtrackingaffordance 1292 to backtrack to a previous user interface, settingsaffordance 1294, a live video indicator 1296, and camera on/off switch1298.

Outside of the video region 1206, the user interface 1204 includesadditional user interface objects and information. For example, the userinterface 1204 includes a timeline 1208 for displaying camera events andtheir corresponding times and durations; a calendar affordance 1230 tojump to a particular calendar day in the timeline 1208; a time scaleselector 1231 for selecting a level of detail in the timeline 1208;arrows 1232 and 1234 for scrolling backward and forward in the timeline,respectively; an activity zone affordance 1229 for accessing a list ofalert event types and user-defined zones of interest for filtering thetimeline by alert event type and/or zone of interest, as well as optionsto create or edit a zone of interest in the area monitored by theassociated camera; and video clip affordance 1233 for accessing a userinterface for creating user-custom video clips from video captured bythe associated camera. The defining of zones of interest is described inthe following U.S. patent applications filed on Oct. 8, 2014, which areincorporated by reference herein in their entirety: Ser. Nos.14/509,999; 14/510,050; 14/510,015; 14/510,029; 14/510,007; 14/510,040;14/510,030; 14/510,042; and14/510,059.

The timeline 1208 shows a chronology of camera events associated withthe associated camera. A camera event includes a corresponding video,one or more alert events that are associated with the video, and thechronology of the associated alert events. The alert events may be anyevent detected in the smart home environment 100 by a smart device 204(e.g., detected hazard, detected sound, detected vibration, operation ofa smart door lock 120, detected motion, etc.); the smart homeenvironment 100 is configured to log and/or alert the user of detectionof such events. In some implementations, alert events include motionevents detected non-visually (e.g., detected by motion detectors) aswell as motion events detected through video captured by a camera 118(e.g., motion through or in a user-defined zone of interest). Detectionof motion activity in a zone of interest is described in the followingU.S. patent applications filed on Oct. 8, 2014, which were incorporatedby reference above: Ser. Nos. 14/509,999; 14/510,050; 14/510,015;14/510,029; 14/510,007; 14/510,040; 14/510,030; 14/510,042; and14/510,059. In some implementations, each zone of interest is its owntype of alert event; motion detected in one zone of interest and motiondetected in another zone of interest are considered different types ofalert events.

In some implementations, when an alert event is detected, one or morecameras 118 proximate to the detected event or proximate to the smartdevices 204 that detected the event are instructed to capture video, soas to capture a visual state of one or more areas proximate in locationto, and contemporaneous (or otherwise proximate in time) with, thedetected alert event. The alert event is associated with the capturedvideo.

The smart devices 204 may detect concurrent, overlapping, or sequencedalert events. Any two alert events that are in sequence with a less thana threshold amount of time (e.g., 2 seconds) between them, concurrent,or overlapping are associated with the same camera event. Thus, a cameraevent and its corresponding video may be associated with multiple alertevents (e.g., detected sound and vibration at same time, motion detectedacross multiple zones of interest in sequence).

A time marker 1236 is displayed on the timeline 1208. The time marker1236 indicates the time in focus on the timeline 1208 and in the videoregion 1206. In FIG. 12A, the time marker 1236 is displayed at therightmost end of the timeline 1208, at a position between the solidportion and the dotted portion. The dotted portion indicates futuretime, and the solid portion includes past time up to the present. Insome implementations, past time on the timeline 1208 in which the camerawas off may also be represented as a dotted portion on the timeline1208. Thus, the time marker 1236, positioned as shown in FIG. 12A, ismarking the current time.

Camera events are represented on the timeline by bars 1238 displayedover (e.g., overlaid on) the timeline 1208. Each bar 1238 has a lengthreflecting the duration of the camera event. For example, the cameraevent 1238-A is longer than the camera event 1238-B. In someimplementations, the duration of a camera event is from the start of theearliest alert event in the camera event to the end of the last alertevent in the camera event.

It should be appreciated that camera events may or may not be displayedas bars 1238, depending on the fineness of the time scale of thetimeline 1208. For example, camera events that are too short in durationto be displayed as bars for a particular time scale (e.g., a 5 secondcamera event at the hours scale) may be displayed as a shaped dot on thetimeline 1208.

In some implementations, one or more icons 1240 corresponding to typesof alert events are displayed in or near respective camera event bars1238 to indicate the alert events associated with the respective alertevents. For example, icons 1240-A, 1240-B, and 1240-C are displayed incamera event bar 1238-A; and icons 1240-A, 1240-B, and 1240-C, and1240-D are displayed in camera event bar 1238-B. Each icon correspondsto a respective type of alert event, and visually distinct from eachother. In some implementations, the visual distinction is based onshape. For example, as shown in FIG. 12A, icon 1240-A is a circle, icon1240-B is a hexagon, icon 1240-C is a triangle, and icon 1240-D is asquare. In some other implementations, the visual distinction is basedon color. For example, the icons 1240 may be circles of differentcolors.

In some implementations, the shape or color definitions for the icons1240 may be automatically defined and/or user-defined. For example,shapes or colors for icons 1240 corresponding to predefined alert eventtypes (e.g., hazard, sound, vibration, non-visual motion) are definedaccording to a default scheme, and shapes or colors for icons 1240corresponding to user-defined zones of interest are defined according tothe default scheme or user definition.

In some implementations, if multiple instances of a particular type ofalert event were detected during a camera event, the icon 1240corresponding to that particular type is displayed just once within thecamera event bar 1238.

In some implementations, the icons 1240 displayed within a camera eventbar 1238 are ordered within the camera event bar 1238. In someimplementations, the ordering is based on the chronological order of thealert events in the camera event. For example, in FIG. 12A, the icons1240 within a camera event bar are ordered from left to right, with thefurther right icons within the camera event bar 1238 corresponding toalert events more recent in time. In camera event 1238-A, there may beone or more multiple instances of the alert type of the typecorresponding to icon 1240-C detected, but the most recent instance ofthat type is also the most recent alert event detected within thecorresponding camera event, and thus the icon 1240-C is displayed in theright-most position. In some other implementations, the icons 1240displayed within a camera event 1238 are randomly ordered.

In some implementations, the icons 1240 within a camera event bar 1238are ordered based on the chronological order of the most recentinstances of each detected type of alert event, as just one icon isdisplayed for each type of alert event detected. Within the camera eventbar 1238-A, an instance of the alert event of the type corresponding toicon 1240-C is the most recent alert event for the corresponding cameraevent and is more recent than the most recent instance of the alertevent type corresponding to icon 1240-B detected for the correspondingcamera event. As another example, within the camera event bar 1238-B,the most recent instance of the alert event type corresponding to icon1240-D is more recent than the most recent instance of the alert eventtype corresponding to icon 1240-A, and thus icon 1240-D is displayed tothe right of icon 1240-A.

In some implementations, if alert event type icons 1240 aredistinguished based on color, and a camera event includes just one alertevent type, then the corresponding camera event bar 1238 may bedisplayed with the color corresponding to the alert event type.

A user may click on (e.g., with a mouse) or tap on (e.g., with a contacton a touch screen) or hover over (e.g., with a mouse pointer) a cameraevent 1238 to view additional information about the camera event. Forexample, in FIG. 12B, a mouse pointer 1241 is hovered over camera eventbar 1238-A. In response to the hovering mouse pointer, an informationpop-up 1242 for the camera event 1238-A is displayed. The informationpop-up 1242 includes a thumbnail 1244 of the video associated with thecamera event 1238-A; date and time information 1246 for the cameraevent; and icons 1240, ordered chronologically in same manner as theicons 1240 within camera event bar 1238-A, corresponding to alert eventtypes detected for the camera event 1238-A. In some implementations, thethumbnail 1244 is the video corresponding to the camera event 1238-Aplayed back at the thumbnail size. In some other implementations, thethumbnail 1244 is a still image (e.g., a frame) from the videocorresponding to the camera event 1238-A.

In some implementations, the time marker 1236 may be moved (e.g.,dragged) along the timeline 1208 by the user to “scrub” the timeline1208 and manually jump to a desired time in the timeline 1208. FIG. 12Cillustrates an example of “scrubbing” the timeline 1208, where the timemarker 1236 has been moved to a position over the camera event bar1238-A. In response to the time marker 1236 being positioned over thecamera bar 1238-A, a preview bar 1248 is displayed. The preview bar 1248includes a chronological sequence of thumbnails 1250 of still frames ofthe video associated with the camera event 1238-A. The thumbnail 1250-Ais the thumbnail of the still frame closest in time to the timecorresponding to the timeline 1208 position where time marker 1236 ispositioned. Thumbnails 1250-B and 1250-C are the next thumbnails afterthumbnail 1250-A in the chronological sequence. Thumbnails 1250-D and1250-E are the previous thumbnails before thumbnail 1250-A in thechronological sequence. With each thumbnail 1250, the time of the framecorresponding to the thumbnail 1252 and icons 1240 are displayed. Insome implementations, the icons 1240 displayed for each thumbnailinclude just the icons corresponding to alert event types for whichinstances are detected at the same time as the time of the framecorresponding to the thumbnail.

In some implementations, the user-defined zones of interest may bedisplayed in the video region 1206 over the video feed 1207. Forexample, when affordance 1229 is activated, a filtering list ofuser-defined zones of interest and alert event types is displayed, aswell as options to edit and create, respectively, a zone of interest(not shown). The user may select one or more of the zones and alertevent types for filtering of the timeline 1208 and the camera eventstherein by the selected zones and alert event types. The user may alsoselect the option to edit a zone. In response to the user selecting theoption to edit a zone, the defined zones are displayed in the videoregion 1206 while the video feed 1207 continues to be played in videoregion 1206, along with a prompt for the user to select a zone forediting. For example, FIG. 12D shows zones 1254-A and 1254-B displayedin the video region 1206 over the video feed 1207 while the video feed1207 continues to play, and a prompt 1260 for a user to select one ofthe displayed zones 1254 for editing. If zones are associated withrespective colors, the zones 1254-A and 1254-B are displayed in theirrespective associated colors. Zones of interest are described in thefollowing U.S. patent applications filed on Oct. 8, 2014, which wereincorporated by reference above: Ser. Nos. 14/509,999; 14/510,050;14/510,015; 14/510,029; 14/510,007; 14/510,040; 14/510,030; 14/510,042;and 14/510,059.

In some other implementations, instead of being an affordance foropening a user interface for filtering zones of interest and alert eventtypes, the affordance 1229 is an affordance for toggling between showingand not showing zones of interest in the video region 1206, aside fromany filtering of the timeline 1208 or any option edit or create a zoneof interest.

As described above, icons 1240 may be displayed within or near a cameraevent bar 1238. FIG. 12E illustrates an example of icons 1240 displayednear (e.g., above) camera event bars 1238. For example, icons 1240-A,1240-B, and 1240-C are displayed above camera event bar 1238-A; andicons 1240-B, 1240-A, 1240-D, and 1240-C are displayed above cameraevent bar 1238-B. The icons for a respective camera event bar 1238 areordered in accordance with the same criteria as those described above inrelation to FIG. 12A. Thus, for example, for camera event 1238-A, icon1240-C corresponding to the alert event type with the most recentlydetected instance.

FIGS. 13A-13M illustrate example user interfaces on a client device forreviewing a camera history in accordance with some implementations. FIG.13A illustrates a camera history user interface 1304 for a respectivecamera 118 (in FIG. 13A et al., the associated camera 118 is the “Diningroom” 1118-C (FIG. 11A) camera 118), displayed by a client device 504(e.g., a mobile device such as a smart phone) on a touch screen 1302. Insome implementations, the camera history user interface 1304 is a partof the same smart home application as user interface 1104 (FIG. 11A etal). User interface 1304 includes an interface title 1306 (e.g.,indicating that the interface corresponds to a camera history);backtracking affordance 1308 to backtrack to a previous user interface(e.g., to user interface 1166 (FIG. 11T)); filtering affordance 1310; aseparator bar 1312 with date indicator 1314, hour indicator 1326, andday forward affordance 1318 and day backward affordance 1320 for jumpingto the next day or the previous day in the camera history, respectively;and a scrollable list of chronologically ordered camera event entries1322-A, 1322-B, 1322-C, 1322-D, 1322-E, and 1322-F.

Each camera event entry 1322, which corresponds to a respective cameraevent associated with the respective camera 118, includes a thumbnail1328 (e.g., a still frame from the video associated with the cameraevent), an activity type identifier 1330, a timestamp 1332 and aduration indicator 1334. For example, the camera event entry 1332-A hasthe thumbnail 1328-A. The corresponding camera event includes motionactivity (as indicated by activity type identifier 1330-A), started at12:49 PM (as indicated by timestamp 1332-A), and lasted 12 seconds (asindicated by duration indicator 1334-A). As another example, the cameraevent entry 1332-B has the thumbnail 1328-B. The corresponding cameraevent includes motion activity (as indicated by activity type identifier1330-B), started at 12:10 PM (as indicated by timestamp 1332-B), andlasted 29 seconds (as indicated by duration indicator 1334-B).

The activity type identifier 1330 for a camera event identifies the typeof the only or primary alert event detected for the camera event. Forexample, in FIGS. 13A-13B, each of the camera events corresponding toentries 1322-A thru 1322-I have detected motion activity (e.g.,detection of motion in a zone of interest or detection of motion throughnon-visual sensors) as the only or primary alert event. In someimplementations, the primary alert event among alert events associatedwith a respective camera event is the most recent among the alertevents. In some other implementations, the primary alert event amongalert events associated with a respective camera event is the one amongthe alert events with the longest duration.

In the separator bar 1312, the hour indicator 1316 identifies the hourof the day identified by date indicator 1314 in which the camera eventscorresponding to the camera event entries 1322 displayed highest (i.e.,closet to the separator bar 1312) in the scrollable list at the momentare detected. Hour separator bars 1324, each of which includes an hourindicator 1326, are displayed to separate camera event entries 1322 byhour. For example, camera event entries 1322-A and 1322-B correspond tocamera events that occur in the 12 PM hour, and camera event entries1322-C, 1322-D, 1322-E, and 1322-F correspond to camera events thatoccur in the 11 AM hour.

As described above, the list of camera event entries 1322 is scrollable.For example, in FIG. 13A, upward swipe gesture 1338 with contact 1336 isdetected on the touch screen 1302. In response to the swipe gesture, thelist of camera event entries 1322 is scrolled upward, the result ofwhich is illustrated in FIG. 13B. Entries 1322-D, 1322-E, and 1322-Fhave moved upward; entries 1322-A, 1322-B, and 1322-C have scrolled outof view; and entries 1322-G, 1322-H, and 1322-I have scrolled into view.The hour indicator 1316 in separator bar 1312 is updated to reflect thehour of day when the camera events corresponding to scrolled-up entries1322-D, 1322-E, and 1322-F occurred. Hour separator bar 1324-A isscrolled out of view, and hour separator bar 1324-B is scrolled intoview. Hour separator bar 1324-B identifies the hour day when the cameraevents corresponding to entries 1322-G, 1322-H, and 1322-I occurred.

An individual camera event entry 1322 may be expanded to display furtherinformation about the corresponding camera event. For example, FIG. 13Billustrates a gesture (e.g., a single tap gesture with contact 1340)detected on camera event entry 1322-E. In response to detecting thegesture on camera event entry 1322-E, camera event entry 1322-E isexpanded inline into a video player interface 1342, as shown in FIG.13C. The video player interface 1342 includes an activity typeidentifier 1344, a timestamp 1346 and a duration indicator 1348. Theactivity type identifier 1344, timestamp 1346 and duration indicator1348 repeats the information shown in the activity type identifier1330-E, timestamp 1332-E, and duration indicator 1334-E (FIG. 13B) forcamera event entry 1322-E, respectively.

The video player interface 1342 also displays information on the typesof alert events associated with the corresponding camera event, i.e.,types of alert events (including zones of interest) detected andassociated with the camera event. The alert event type informationincludes alert event type identifiers 1350 and corresponding icons 1352.For example, in the video player interface 1342, alert event types(including zones of interest) “Table,” “Window,” and “Sound” areassociated with the camera event corresponding to camera event entry1322-E; alert events of the types “Table,” “Window,” and “Sound” weredetected and associated with the corresponding video 1354 and thecorresponding camera event. As with icons 1240, icons 1352 may bedistinguished by shape or color associated with respective alert eventtypes and zones. If the icons 1352 are distinguished based on color, thecorresponding labels 1350 may also be displayed in the correspondingassociated colors as well.

The video player interface 1342 includes the video 1354 associated withthe corresponding camera event. In FIG. 13C, the scene in the video 1354includes a person 1359, a window 1360, and a table 1362. A playbackprogress bar 1356 represents the full length of the video 1354, with theshaded portion 1358 representing the playback progress of the video 1354so far.

In some implementations, playback of the video 1354 is automaticallystarted when the camera event entry 1322-E is expanded into the videoplayer interface 1342. In some other implementations, playback ismanually started; playback affordance 1364 is displayed over the video1354, as shown in FIG. 13D, and playback is started by the userperforming a gesture (e.g., a single tap) on the playback affordance1364. Before the video 1354 finishes playback, the user may togglebetween playing the video 1354 and pausing the video 1354 by performinga gesture (e.g., a single tap) on the video 1354. While the video 1354is playing or paused, the user may collapse the video player interface1342 back to the camera event entry 1322-E by performing a gesture(e.g., a single tap) on an area in the video player interface 1342outside of the video 1354 (e.g., single tap gesture with contact 1366outside of video 1354, as shown in FIG. 13C).

When playback of the video 1354 is complete (as indicated by theplayback progress bar 1356 being completely filled 1358; in some otherimplementations the playback progress bar 1356 is omitted from displaywhen the playback is complete), replay affordance 1370 and continueaffordance 1372 are displayed over the video 1354. The user may performa gesture (e.g., a single tap) on the replay affordance 1370 to have thevideo 1354 replayed from the start.

In some implementations, the user may perform a gesture (e.g., a singletap) on the continue affordance 1372 to replace the user interface 1304with user interface 1166 for the associated camera 118 and play the nextvideo from the associated camera 118 in the user interface 1166 fromwhere the video 1354 left off.

The user may collapse the video player interface 1342 back to the cameraevent entry 1322-E by performing a gesture (e.g., a single tap) on anarea in the video player interface 1342 outside of the video 1354 (e.g.,single tap gesture with contact 1374 outside of video 1354, as shown inFIG. 13E).

FIGS. 13A-13B illustrates a scrollable list of camera event entries 1322in which each of the entries 1322 in the list correspond to cameraevents in which the only or primary alert event is detected motionactivity. FIG. 13F illustrates an example of a list of camera evententries 1322 with different types of only or primary alert event types.For example, the only or primary alert event for the camera eventcorresponding to entry 1322-J is detected motion (as indicated byidentifier 1330-J). The only or primary alert event for the camera eventcorresponding to entry 1322-K is a detected hazard (as indicated byidentifier 1330-K). The only or primary alert event for the camera eventcorresponding to entry 1322-N is detected sound (as indicated byidentifier 1330-N).

In some implementations, the list of camera event entries 1322 may befiltered to highlight particular alert event types (e.g., particularzones of interest). FIG. 13G illustrates a gesture being detected on thefiltering affordance 1310. In response to detecting the filteringaffordance 1310, a filtering menu 1378 is displayed over an obscureduser interface 1304, as shown in FIG. 13H. The filtering menu 1378includes one or more filtering criteria 1380, a cancel affordance 1386for cancelling filtering, and “Done” affordance 1384 for confirmingselected filtering criteria and proceeding with filtering.

Each filtering criterion 1380 includes an identifier of thecorresponding alert event type 1350 and icon 1352. In FIG. 13H, thefiltering criteria 1380 presented are zones of interest (“Filter byZone”), including the “Table” 1350-A criterion 1380-A, accompanied byicon 1352-A; “Window” 1350-B criterion 1380-B, accompanied by icon1352-B; and “Motion outside zones” 1350-D criterion 1380-C, accompaniedby icon 1352-C. “Motion outside zones” corresponds to motion detectedoutside any of the user-defined zones of interest, such as “Table”1350-A and “Window” 1350-B.

In some implementations, a user selects a filtering criterion byperforming a gesture (e.g., a single tap) over the desired criterion.For example, a single tap gesture with contact 1382 is detected overcriterion 1380-A. In response to detecting the gesture, criterion 1380-Ais checked, indicating selection, as shown in FIG. 13I. The same gesturemay be repeated on criterion 1380-A to deselect the criterion. Thegesture may be performed on other criteria in the menu 1378 to select ordeselect them as desired. When the user has completed selecting thefiltering criteria, the user performs a gesture on the “Done” affordance1384. For example, a single tap gesture with contact 1390 is detected onthe “Done” affordance 1384.

In response to detecting the gesture on the “Done” affordance 1384, theselected filtering criteria are applied. For example, in FIG. 13J, the“Table” 1350-A criterion is applied to the camera event entries 1322.When filtering is active, the criterion being applied (e.g., asidentified by alert event type identifier(s) 1350 and/or icon(s) 1352)is displayed under the interface title 1306. When filtering is applied,camera event entries 1322 corresponding to camera events that have thealert event type for which filtering is applied includes indicators ofthe alert even types being applied. For example, entries 1322-D, 1322-E,and 1322-F include the “Table” identifier 1350-A and corresponding icon1352-A, indicating that the camera events corresponding to these entrieshave motion detected in the “Table” 1350-A zone of interest.

Multiple criteria may be selected for filtering. For example, FIG. 13Killustrates multiple filtering criteria being applied. These multiplecriteria are identified by icons 1352-A (corresponding to “Table”1350-A) and 1352-B (corresponding to “Window” 1352-B). Camera evententries 1322 corresponding to camera events that have the alert eventtype for which filtering is applied includes indicators of the alerteven types being applied. For example, entries 1322-D, 1322-E, and1322-F include the “Table” identifier 1350-A and/or corresponding icon1352-A, indicating that the camera events corresponding to these entrieshave motion detected in the “Table” 1350-A zone of interest. Entries1322-E, 1322-F, 1322-G, 1322-H, and 1322-I include the “Window”identifier 1350-B and/or corresponding icon 1352-B, indicating that thecamera events corresponding to these entries have motion detected in the“Window” 1350-B zone of interest.

Entries 1322-E and 1322-F include both icons 1352-A and 1352-B,indicating that the camera events corresponding to these entries havemotion detected in the “Table” 1350-A zone of interest and in the“Window” 1350-B zone of interest. In some implementations, when multiplefiltering criteria are applied and an entry 1322 meets more than one ofthe filtering criteria, the icons 1352 corresponding to the met criteriaare displayed in an order. The order is a chronological order similar tothat used for icons 1240 (FIG. 12A)—chronological order of the mostrecent instances of each alert event type in question. For example, forentry 1322-E, the most recent instance of motion in the “Window” 1350-Bzone (corresponding to icon 1352-B displayed more to the right), is morerecent than the most recent instance of motion in the “Table” 1350-Azone (corresponding to icon 1352-A). For entry 1322-F, the most recentinstance of motion in the “Table” 1350-A zone (corresponding to icon1352-A displayed more the right) is more recent than the most recentinstance of motion in the “Window” 1350-B zone (corresponding to icon1352-B).

As described above, the filtering criteria 1380 are alert even types,where respective zones of interest are considered as distinct alertevent types. FIG. 13L illustrates a filtering menu 1378 that includesfiltering criteria 1380 that includes zones of interest and other typesof alert events. In addition to criteria 1380-A, 1380-B, and 1380-C,described above in relation to FIG. 13I, the filtering menu 1378 alsoincludes criteria 1380-D, 1380-E, 1380-F, and 1380-G. Criterion 1380-Dcorresponds to the “Sound” 1350-C alert event type. Criterion 1380-Ecorresponds to the “Vibration” 1350-E alert event type. Criterion 1380-Fcorresponds to the “Hazard” 1350-F alert event type. Criterion 1380-Gcorresponds to the “Motion” 1350-G (or more particularly, motiondetected by sensors other than cameras 118, e.g., motion sensors) alertevent type. The criteria 1380 may be selected and applied as describedabove in relation to FIGS. 13I-13K.

In some other implementations, alert event type and/or zone labels 1350and icons 1352 are displayed for each entry 1322 by default, even beforeany filtering. In other words, by default, each entry 1322 is displayedwith its associated alert event types and zones information displayed aswell. When filtering, entries that satisfy the filtering criteria aredisplayed with all of their associated alert event types and zones(i.e., none are omitted and none are specifically highlighted), andentries that do not meet the filtering criteria 1322 (i.e., notassociated with at least one alert event type or zone selected for thefiltering criteria) are not displayed. Thus for example, in FIG. 13Jentries 1322-G, 1322-H, and 1322-I would not be displayed when filteringby the “Table” zone.

FIGS. 13A-13L illustrate a camera history for one camera 118. FIG. 13Millustrates an example of a camera history for multiple cameras 118. Thescrollable list of entries 1322 include entries 1322-P, 1322-Q, 1322-S,and 1322-U corresponding to camera events associated with a first camera(e.g., “Outside” 1118-A camera), entry 1322-R corresponding to a cameraevent associated with a second camera (e.g., “Front door” 1118-Bcamera), and entry 1322-T corresponding to a camera event associatedwith a third camera (e.g., “Dining room” 1118-C camera).

In some implementations, one or more of the functionalities describedabove in relation to FIGS. 11A-13M (e.g., changing view displayed incamera object 1116, accessing camera history user interface 1304, etc.)may be activated by respective predefined voice inputs or commands.

Exemplary Processes

FIGS. 14A-14E illustrate a flowchart diagram of a method 1400 forpresenting multiple video feeds in accordance with some implementations.In some implementations, the method 1400 is performed by an electronicdevice with one or more processors, memory, a display, and optionally atouch screen, an accelerometer, and/or an audio input device. Forexample, in some implementations, the method 1400 is performed by clientdevice 504 (FIGS. 5A-5B and 8) or one or more components thereof (e.g.,client-side module 502, presentation module 821, input processing module822, web browser module 823, application 824, user interface module826). In some implementations, the method 1400 is governed byinstructions that are stored in a non-transitory computer readablestorage medium (e.g., the memory 806) and the instructions are executedby one or more processors of the electronic device (e.g., the CPUs 802).Optional operations are indicated by dashed lines (e.g., boxes withdashed-line borders).

In an application executing at the electronic device (e.g., clientdevice 504), the electronic device receives a plurality of video feeds,each video feed of the plurality of video feeds corresponding to arespective remote camera of a plurality of remote cameras, wherein thevideo feeds are received concurrently by the device from a server systemcommunicatively coupled to the remote cameras (1402). The client device504, for example, receives respective video feeds from multiple cameras118 through the hub device server system 508 or video server system 552.Each of the received video feeds corresponds to a respective camera 118.

The electronic device displays a first user interface, the first userinterface including a plurality of user interface objects, each userinterface object of the plurality of user interface objects beingassociated with a respective remote camera of the remote cameras (1404).The client device 504 displays a user interface 1104 that includes oneor more camera objects 1116 (FIG. 11A). Each camera object 1116 isassociated with a respective camera 118. For example, camera object1116-A is associated with the “Outside” 1118-A camera, camera object1116-B is associated with the “Front door” 1118-B camera, and cameraobject 1116-C is associated with the “Dining room” 1118-C camera.

The electronic device displays in each user interface object of theplurality of user interface objects the video feed corresponding to therespective remote camera with which the user interface object isassociated, wherein at least one of the video feeds is displayed withcropping (1408). The client device 504 displays in each camera object1116 the video feed from the respective associated camera 118. Forexample, the video feed from the “Outside” 1118-A camera is displayed inthe camera object 1116-A as view 1120, the video feed from the “Frontdoor” 1118-B camera is displayed in the camera object 1116-B as view1122, and the video feed from the “Dining room” 1118-C camera isdisplayed in the camera object 1116-C as view 1124. Each of the videofeeds is displayed with cropping (e.g., as described above in relationto FIG. 11B), as opposed to, for example, zooming out (i.e.,de-magnifying) the video feed to fit the frames of the feed into thecamera object 1116.

In some implementations, each respective remote camera of the pluralityof remote cameras has a respective field of view, and a user interfaceobject associated with a respective remote camera has a virtual field ofview relatively smaller than the respective field of view of theassociated respective remote camera (1406). As shown in FIG. 11B, eachrespective camera 118 has a field of view represented by the full framesize 1117. The camera object 1116 is relatively smaller than the fullframe size 1117.

In some implementations, displaying in each user interface object of theplurality of user interface objects the video feed corresponding to therespective remote camera with which the user interface object isassociated comprises displaying, in a respective user interface object,periodically refreshed still images corresponding to frames from thecorresponding video feed (1410). One or more of the video feeds may bedisplayed in their respective camera objects 1116 as periodicallyrefreshed (e.g., at 1 image per second, 1 image per two seconds, etc.)images (e.g., still frames from the video feed).

In some implementations, the electronic device receives a first userinput to adjust a cropping of one or more of the video feeds displayedin the user interface objects (1414). In response to receiving the firstuser input, the electronic device adjusts the cropping of the one ormore video feeds displayed in the user interface objects (1422). Theclient device 504, for example, while displaying the video feeds in thecamera objects 1116, receives an input to adjust the views 1120, 1122,and 1124 of the video feeds (e.g., gesture 1138, orientation change1129, a predefined voice input (not shown)). In response to the input,the views 1120, 1122, and 1124 of the video feeds are adjusted, as shownin FIG. 11D; a respective view is panned so that a different area of thevideo feed is cropped.

In some implementations, the views displayed in the camera objects 1116are selectively adjustable. For example, FIGS. 11H-11K illustrate cameraobjects 1116-A and 1116-B selected, and then a gesture 1148 to activateview adjustment is detected. In response to the gesture 1148, thecroppings of the views 1120 and 1122, corresponding to the selectedcamera objects 1116-A and 1116-B are adjusted, with the results beingviews 1120-2 and 1122-2. View 1124 is not adjusted as camera object wasnot selected prior to the gesture 1148.

In some implementations, the mobile device comprises an accelerometer,and the first user input comprises a change, by a user, of anorientation of the mobile device. The electronic device receives a firstuser input to adjust a cropping of one or more of the video feedsdisplayed in the user interface objects by detecting the change of theorientation of the mobile device using the accelerometer (1416). Theelectronic device adjusts the cropping in response to receiving thefirst user input by adjusting the cropping of the one or more videofeeds in accordance with the orientation change (1424). For example, asshown in FIG. 11C, the client device 504 may be rotated 1129 to changeits orientation. The orientation change is detected by the accelerometer892. In response to the orientation change, the views 1120, 1122, and1124 in the camera objects 1116 are changed in accordance with theorientation change. For example, a clockwise rotation 1129 of the clientdevice 504 causes the views 1120, 1122, and 1124 to respectively shiftrightward relative to the associated camera objects 1116.

In some implementations, the mobile device comprises a touch-sensitivedisplay, and the first user input comprises a gesture performed on thetouch-sensitive display. The electronic device receives a first userinput to adjust a cropping of one or more of the video feeds displayedin the user interface objects by detecting the gesture on thetouch-sensitive display (1418). The electronic device adjusts thecropping in response to receiving the first user input by adjusting thecropping in accordance with the gesture (1426). For example, as shown inFIG. 11C, gesture 1128 may be performed by a user on the touch screen1102. In response to detecting the gesture, the views 1120, 1122, and1124 in the camera objects 1116 are changed in accordance with thegesture. For example, a rightward gesture 1128 on the touch screen 1102causes the views 1120, 1122, and 1124 to respectively shift rightwardrelative to the associated camera objects 1116.

In some implementations, the mobile device comprises an audio inputdevice, and the first user input comprises a voice command. Theelectronic device receives a first user input to adjust a cropping ofone or more of the video feeds displayed in the user interface objectsby detecting the voice command using the audio input device (1420). Theelectronic device adjusts the cropping in response to receiving thefirst user input by adjusting the cropping in accordance with the voicecommand (1428). For example, the user may issue a predefined voicecommand instructing the smart home application running on the clientdevice 504 to adjust the views displayed in the camera objects 1116. Inresponse to detecting the voice command, the views 1120, 1122, and 1124in the camera objects 1116 are changed in accordance with the voicecommand.

In some implementations, prior to receiving the first input, theelectronic device receive a second user input selecting one or more userinterface objects of the plurality of the user interface objects (1412).Adjusting the cropping in response to receiving the first user inputcomprises adjusting the cropping of only the video feeds displayed inthe selected user interface objects in accordance with the first userinput (1430). For example, the client device 504 may receive one or moreinputs (e.g., gestures with contacts 1142 and 1144, FIGS. 11H-11I). Inresponse to these inputs, one or more camera objects 1116 (e.g., cameraobjects 1116-A and 1116-B) are selected, as shown in FIG. 11J. Withcamera objects 1116-A and 1116-B selected, in response to detecting userinput to change the views displayed in the camera objects (e.g., gesture1148, orientation change 1149, predefined voice input), just the views1120 and 1122 in camera objects 1116-A and 1116-B are adjusted.

In some implementations, the electronic device receives a third userinput to lock the cropping of the one or more of the video feeds (1432).In response to receiving the third user input, the electronic devicemaintains the adjustment of the cropping of the one or more of the videofeeds (1434). In FIG. 11D, for example, after the views 1120, 1122, and1124 are adjusted in response to detecting the gesture 1128, the usermay perform a gesture (e.g., a single tap) with contact 1127 before theviews reset to their previous states. In response to that gesture, theviews 1120-2, and 1122-2, and 1124-2 are maintained instead of resettingto views 1120-1, and 1122-1, and 1124-1.

In some implementations, the electronic device detects a termination ofthe first user input (1436), and in response to detecting thetermination of the first user input, maintains the adjustment of thecropping (1438). In FIG. 11D, for example, after the views 1120, 1122,and 1124 are adjusted to views 1120-2, and 1122-2, and 1124-2 inresponse to detecting the gesture 1128, the user may terminate thegesture 1128 by lifting the contact 1126 off the touch screen 1102. Insome implementations, in response to the termination of the gesture1128, the views 1120-2, and 1122-2, and 1124-2 are maintained.

In some implementations, the electronic device detects a termination ofthe first user input (1440), and in response to detecting thetermination of the first user input, ceases the adjustment of thecropping (1442). In FIG. 11D, for example, after the views 1120, 1122,and 1124 are adjusted to views 1120-2, and 1122-2, and 1124-2 inresponse to detecting the gesture 1128, the user may terminate thegesture 1128 by lifting the contact 1126 off the touch screen 1102. Insome implementations, in response to the termination of the gesture1128, the views 1120-2, and 1122-2, and 1124-2 are automatically resetto views 1120-1, 1122-2, and 1122-4.

In some implementations, while the application is in a foreground, thevideo feeds are received and displayed in the user interface objects asvideo streams; and while the application is in a background, the videofeeds are received as periodically refreshed still images correspondingto frames from the video feeds (1444). The smart home application may bein the foreground (and its user interface displayed) or in thebackground (and not displayed) at any given moment. When the smart homeapplication is in the foreground, the smart home application may receivethe video feeds for the camera objects 1116 as video streams. When thesmart home application is in the background, the smart home applicationmay receive the video feeds for the camera objects 1116 in thebackground as periodically refreshed images instead of video streams.

In some implementations, each respective video feed of the plurality ofvideo feeds comprises a first version at a first resolution and a secondversion at a second resolution higher than first resolution, and boththe first version and the second version are received from the serversystem (1446). In some implementations, the client device 504 receiveseach video feed from the hub device server system 508 or the videoserver system 552 in both an original capture resolution (e.g., 720P or1080P) version and a lower-resolution version (e.g., 180P).

In some implementations, the video feeds displayed in the user interfaceobjects are the first versions (1448). The lower-resolution version(e.g., the 180P version) is displayed in the camera objects 1116.

In some implementations, the first version of a respective video feed isdisplayed in an associated user interface object (1450). The electronicdevice receives user selection of the associated user interface object(1452), and in response to receiving the user selection, ceases displayof the first user interface and displays a second user interface, thesecond user interface including the second version of the respectivevideo feed, wherein within the second user interface the respectivevideo feed is uncropped (1454). As described above, the lower-resolutionversion of a video feed is displayed in the corresponding camera object1116. For example, the 180P version of the “Dining room” 1118-C cameravideo feed is displayed in the camera object 1116-C. As shown in FIG.11S, while the “Dining room” 1118-C camera video feed is displayed in acamera object 1116-C, a single tap gesture with contact 1164 is detectedon the camera object 1116-C. In response to detecting the gesture, userinterface 1166 (FIG. 11T) is displayed on the touch screen 1102,replacing user interface 1104. The “Dining room” 1118-C camera videofeed is displayed in video region 1180 without cropping and at a higherresolution than that for the camera object 1116-C (e.g., at the originalcapture resolution).

In some implementations, the cropping of the at least one of the videofeeds is performed at the mobile device in accordance with instructionsfrom the server system, wherein the cropping instructions are generatedby the server system based on an analysis of the at least one of thevideo feeds by the server system to determine a portion of the at leastone of the video feed of potential interest to a user (1456). Thecropping may be performed by the hub device server system 508 or thevideo server system 552. The hub device server system 508 or the videoserver system 552 crops a video feed before transmitting the video feedto a client device 504. In some implementations, the cropping by theserver system 508 or 552 is based on an analysis by the server system508 or 552 of a video feed to be cropped to determine which portion ofthe video feed (e.g., which portion of the frame) is of potentialinterest to the user. For example, the servers system 508 or 522 may,based on an analysis of the video feed, determine that there is motionoccurring in the video, and crops the video feed to focus on that motion(e.g., crop the video feed to focus on the area where the motionoccurred).

In some implementations, a plurality of the video feeds is displayedwith cropping, and each of the cropped video feeds is cropped inaccordance with a same cropping mask (1458). For example, in FIG. 11Athe video feeds displayed in the camera objects 1116-A, 1116-B, and1116-C are cropped. As the camera objects camera objects 1116-A, 1116-B,and 1116-C all have the same circular shape and size, the video feedsare cropped with the same cropping mask that fits the video feeds intothe same circular shape and size. In some implementations, all of thevideo feeds displayed in the camera objects 1116 are cropped. In someother implementations, some of the video feeds displayed in the cameraobjects 1116 are cropped; one or more of the feeds are instead zoomedout within the camera object 1116 to fit the entire frame 1117 into thecamera object. In some implementations, each video feed is cropped tosame mask or mask shape; the mask or mask shape is based on the shapeand size of the camera objects 1116. In some other implementations, eachcamera object 1116 has a distinct shape, and the correspondingmasks/mask shapes differ in accordance with the distinct shapes of thecamera objects 1116.

FIGS. 15A-15B illustrate a flowchart diagram of a method 1500 for savingalert events in a camera history in accordance with someimplementations. In some implementations, the method 1500 is performedby a server system (of one or more server computers) with one or moreprocessors and memory. For example, in some implementations, the method1500 is performed by hub device server system 508 or video server system552 (FIGS. 5A-5B and 7A-7D) or one or more components thereof (e.g.,server-side module 714, FIG. 7A; video server module 730, FIG. 7B). Insome implementations, the method 1500 is governed by instructions thatare stored in a non-transitory computer readable storage medium (e.g.,the memory 706, 722) and the instructions are executed by one or moreprocessors of the electronic device (e.g., the CPUs 702, 718). Optionaloperations are indicated by dashed lines (e.g., boxes with dashed-lineborders).

The server system receives a video feed from a camera with an associatedfield of view (1502). The hub device server system 508 or video serversystem 552 (e.g., the video data receiving module 7302) receives videofeeds from one or more cameras 118. Each camera 118 has a respectivefield of view.

The server system receives one or more alert events (1504). The hubdevice server system 508 or video server system 552 (e.g., the alertevents module 73022) receives detected alert events from smart devices204. For example, whenever a smart device 204 detects an alert event(e.g., a hazard, sound, etc.), the hub device server system 508 or videoserver system 552 receives information corresponding to the detectedalert event (e.g., start time and end time of the alert event, alertevent type).

The server system identifies as a camera event a portion of the videofeed associated in time with the one or more alert events (1512). Forexample, the hub device server system 508 or video server system 552(e.g., the camera events module 73024) correlates alert events orsequences of alert events with portions of the video feed based on whenthe alert events start and end, and from the correlation identify cameraevents, which include a portion of the video feed (e.g., captured videofrom the video feed from a start date/time to an end date/time) and anassociated set of one or more alert events; the alert events areproximate in time (e.g., contemporaneous) with the associated video. Insome implementations, two alert events are associated with the samecamera event if the alert events overlap or occur in succession with atime gap (i.e., time elapsed between one alert event ending and the nextalert event starting) between the two consecutive alert events beingless than a threshold amount.

The server system determines a start time and duration of the cameraevent (1514). The hub device server system 508 or video server system552 (e.g., the camera events module 73024) determines the start time andduration of the camera event based on the times of the associated alertevents. For example, the start time of the earliest alert event of theassociated alert events is determined to be the start time of the cameraevent, and the end time of the alert event of the associated alertevents that ends latest is determined to be the end time of the cameraevent. With these start and end times, the duration o the camera eventmay be determined. Also, the video that is associated with the cameraevent has these start and end times (and optionally plus some slack timein either direction (e.g., 1-5 seconds before the start time and/or 1-5seconds after the end time)).

The server system determines a chronological order of the alert events(1516). The hub device server system 508 or video server system 552(e.g., the alert events module 73022) determines the chronologicalsequence of the alert events associated with the camera event. In someimplementations, the chronological order is determined based on thestart times of the alert events (i.e., when the respective alert eventsare first detected). In some implementations, the chronological order isdetermined based on the end times of the alert events (i.e., when therespective alert events are last detected).

The server system saves, in a history associated with the camera,information associated with the camera event, including a video clipand/or a frame from the portion of the video feed, and the chronologicalorder of the alert events (1518). The hub device server system 508 orvideo server system 552 saves, in the server database 732 (e.g., incamera events history 7328 and video storage database 7320), theinformation associated with the camera event. The camera eventsinformation (e.g., the associated alert events and correspondingchronology, camera event times and durations, etc.) is stored in thecamera events history 7328, and the camera events information referencesvideo stored in the video storage database 7320.

In some implementations, the alert events include one or more of: ahazard alert event, an audio alert event, a vibration alert event, and amotion alert event (1506). The alert events may be detected hazards(e.g., detected by smart hazard detectors 104), detected sound above aminimum decibel threshold (e.g., detected by any smart device 204 withaudio input), detected vibrations above a minimum threshold (e.g.,detected by any smart device 204 with vibration sensors), and detectedmotion (e.g., detected in video captured by a camera 118 or detected bynon-camera sensors, such as motion sensors).

In some implementations, the motion alert event corresponds to motiondetected in a defined spatial zone associated with the field of view(1508). The motion alert event may correspond to motion detected invideo by the camera 118, where the motion is occurring in a defined zoneof interest in the scene or area monitored by the camera 118. The zoneof interest is a zone designating a space in the scene or area monitoredby the camera 118 for which detected motion is treated as a distinctalert event type in addition to being treated as detected motiongenerally.

In some implementations, the spatial zone is defined by a user (1510).The spatial zone may be defined by a user. The user may enter into auser interface which shows video captured by the camera 118 and mark offa portion in the video as the zone of interest. For example, if thecamera is monitoring a scene that includes a door, the user may mark offthe door as the zone of interest (e.g., by marking a zone boundaryaround the door); motion detected in the door zone is treated as adistinct alert event type. In some implementations, the user isassociated with the camera 118; the camera 118 is tied to the user'saccount (e.g., in account database 7324 and device information database7326).

In some implementations, the server system associates each of the alertevents with a respective visually distinctive display characteristic(1520). The hub device server system 508 or video server system 552associates each alert event type with a visually distinctive displaycharacteristic, so that, when indicators (e.g., icons) of alert eventsare displayed, the user can identify and differentiate between alertevent types based on the distinctive display characteristics, which theindicators adopt. In some implementations, these associations are madeper user. Multiple users may have the same mappings of alert event typesto display characteristics, but it is sufficient that for any onerespective user each alert event type is mapped to a distinct displaycharacteristic. For example, FIGS. 12A and 13C illustrate iconsindicating alert event types 1240 and 1350, respectively, with distinctshapes.

In some implementations, the display characteristic is visuallydistinctive based on color (1522). In some implementations, the displaycharacteristic is visually distinctive based on shape (1524). The alertevent types may be distinct based on the color or shape of theircorresponding indicators. For example, for a respective user, the hazardalert event type is assigned red, the sound alert event type is assignedblue, the vibration alert event type is assigned orange, the generalmotion event type is assigned brown, and motion in a particularuser-defined zone of interest is assigned green. Then, for that user,icons indicating hazard alert events are red, icons indicating soundalert events are blue, icons indicating vibration alert events areorange, etc. Similarly, icons indicating different alert event types mayhave different shapes. For example, FIGS. 12A and 13C illustrate iconsindicating alert event types 1240 and 1350, respectively, with distinctshapes.

In some implementations, the server system, responsive to a request froma client device, transmits contents of the history to the client devicefor display in a desktop browser application at the client device, wherethe contents of the history is formatted for display in the desktopbrowser application as a camera history timeline (1526). For example,when interface 1204 or 1304 is accessed, a request is made to the hubdevice server system 508 or video server system 552 for the history ofthe camera 118. In response to the request, the hub device server system508 or video server system 552 transmits camera history information tothe client device 504 for display. The camera history information may bedisplayed differently depending on the interface (e.g., displayeddifferently in interface 1204 than in 1304). For example, in interface1204, the camera history information is displayed in a linear timeline1208.

In some implementations, the camera history timeline comprises an eventbar corresponding to the camera event, where a length of the event barreflects the duration of the camera event; and one or more alert eventindicators proximate to the event bar, each of the alert eventindicators corresponding to a respective alert event associated with thecamera event, wherein each respective alert event indicator has arespective visually distinctive display characteristic associated withthe corresponding respective alert event (1528). The timeline 1208 mayinclude an event bar 1238 for each camera event. The length of the eventbar 1238, which is to scale relative to timeline 1208, indicates aduration of the camera event. One or more alert event icons 1240 aredisplayed in proximity to the event bar 1238 (e.g., within the event bar1238 (FIG. 12A), near the event bar 1238 (FIG. 12E). The icons 1240 havedistinctive shapes and/or colors mapped to alert event types; the usercan identify the alert event types indicated by the icons 1240 based onthe shapes and/or colors.

In some implementations, the alert event indicators are ordered inaccordance with the chronological order of the alert events (1530). Theicons 1240 are ordered, while displayed, based on the chronologicalorder of the alert events indicated. In some implementations, the icons1240 are ordered based on the chronological order of the most recentinstance of each alert event type for that camera event.

In some implementations, responsive to a request from a client device,the serve system transmits contents of the history to the client devicefor display in a mobile application at the device, where the contents ofthe history is formatted for display in the mobile application as ascrollable camera history list, the scrollable camera history listincluding one or more chronologically ordered event identifiers, eachevent identifier corresponding to a respective camera event (1532). Forexample, when interface 1204 or 1304 is accessed, a request is made tothe hub device server system 508 or video server system 552 for thehistory of the camera 118. In response to the request, the hub deviceserver system 508 or video server system 552 transmits camera historyinformation to the client device 504 for display. The camera historyinformation may be displayed differently depending on the interface(e.g., displayed differently in interface 1204 than in 1304). Forexample, in interface 1304, the camera history information is displayedas a scrollable list of event identifiers 1322 (which may still beviewed as a timeline, because the event identifiers are chronologicallyordered and separated by hour).

In some implementations, the scrollable camera history list comprises anevent identifier corresponding to the camera event; and one or morealert event indicators, each of the alert event indicators correspondingto a respective alert event associated with the camera event, where eachrespective alert event indicator has a respective visually distinctivedisplay characteristic associated with the corresponding respectivealert event (1534). The scrollable list of event identifiers 1322displayed in interface 1304 includes event identifiers 1322corresponding to respective camera events. Alert event icons 1350 may bedisplayed in the event identifiers when a filter is applied (e.g., as inFIG. 13J-13K) or by default. The icons 1350 have distinctive shapesand/or colors mapped to alert event types; the user can identify thealert event types indicated by the icons 1350 based on the shapes and/orcolors.

In some implementations, the alert event indicators are ordered inaccordance with the chronological order of the alert events (1536). Theicons 1350 are ordered, while displayed, based on the chronologicalorder of the alert events indicated. In some implementations, the icons1350 are ordered based on the chronological order of the most recentinstance of each alert event type for that camera event.

FIG. 16 illustrate a flowchart diagram of a method 1600 for presenting acamera history in accordance with some implementations. In someimplementations, the method 1600 is performed by an electronic devicewith one or more processors, memory, a display, and optionally a touchscreen, an accelerometer, and/or an audio input device. For example, insome implementations, the method 1600 is performed by client device 504(FIGS. 5A-5B and 8) or one or more components thereof (e.g., client-sidemodule 502, presentation module 821, input processing module 822, webbrowser module 823, application 824, user interface module 826). In someimplementations, the method 1600 is governed by instructions that arestored in a non-transitory computer readable storage medium (e.g., thememory 806) and the instructions are executed by one or more processorsof the electronic device (e.g., the CPUs 802). Optional operations areindicated by dashed lines (e.g., boxes with dashed-line borders).

The client device displays a video feed from a camera or a frame fromthe video feed (1602). For example, in interface 1204, the client device504 displays a video feed 1207 (or a frame from the video feed 1207(e.g., if the video is paused)) in the video region 1206.

The client device, concurrently with displaying the video feed or theframe, displays a camera history timeline (1604), including: displayinga representation of a camera event associated with one or more alertevents in the camera history timeline as a bar overlaid on the eventhistory timeline, the event bar having a length reflecting a duration ofthe camera event (1606); and displaying, proximate to the event bar, oneor more alert event indicators, each of the alert event indicatorscorresponding to a respective alert event of the alert events associatedwith the camera event, wherein each respective alert event indicator hasa respective visually distinctive display characteristic associated withthe corresponding respective alert event (1608). In interface 1204, theclient device 504 displays, concurrently with the video 1207, a timeline1208 with camera event bars 1238 corresponding to respective cameraevents and icons 1240 indicating alert events associated with the cameraevents 1238. The length of a camera event bar 1238 indicates a durationof the corresponding camera event. The icons 1240 are displayed in thecamera event bars 1238 (as in FIG. 12A) or near the camera event bars1238 (as in FIG. 12E).

In some implementations, the display characteristic is visuallydistinctive based on color (1610). In some implementations, the displaycharacteristic is visually distinctive based on shape (1612). The icons1240 have distinctive shapes and/or colors mapped to alert event types;the user can identify the alert event types indicated by the icons 1240based on the shapes and/or colors.

In some implementations, the activity alert indicators are ordered inaccordance with a chronological order of the corresponding alert events(1614). The icons 1240 are ordered, while displayed, based on thechronological order of the alert events indicated. In someimplementations, the icons 1240 are ordered based on the chronologicalorder of the most recent instance of each alert event type for thatcamera event.

FIG. 17 illustrate a flowchart diagram of a method 1700 for presenting acamera history in accordance with some implementations. In someimplementations, the method 1700 is performed by an electronic devicewith one or more processors, memory, a display, and optionally a touchscreen, an accelerometer, and/or an audio input device. For example, insome implementations, the method 1700 is performed by client device 504(FIGS. 5A-5B and 8) or one or more components thereof (e.g., client-sidemodule 502, presentation module 821, input processing module 822, webbrowser module 823, application 824, user interface module 826). In someimplementations, the method 1700 is governed by instructions that arestored in a non-transitory computer readable storage medium (e.g., thememory 806) and the instructions are executed by one or more processorsof the electronic device (e.g., the CPUs 802). Optional operations areindicated by dashed lines (e.g., boxes with dashed-line borders).

The client device displays a camera history timeline (1702), including:displaying a chronologically ordered sequence of event identifiers, eachevent identifier corresponding to a respective camera event, eachrespective camera event associated with one or more respective alertevents (1704); and displaying, for a respective event identifier, one ormore alert event indicators, each of the alert event indicatorscorresponding to an alert event associated with the camera eventcorresponding to the respective event identifier, each of the alertevent indicators displayed with a visually distinctive displaycharacteristic associated with a corresponding alert event (1706). Forexample, in interface 1304, camera history information is displayed as ascrollable list of event identifiers 1322 (which may still be viewed asa timeline, because the event identifiers are chronologically orderedand separated by hour). The scrollable list of event identifiers 1322displayed in interface 1304 includes event identifiers 1322corresponding to respective camera events. Alert event icons 1350 may bedisplayed in the event identifiers when a filter is applied (e.g., as inFIG. 13J-13K) or by default. The icons 1350 have distinctive shapesand/or colors mapped to alert event types; the user can identify thealert event types indicated by the icons 1350 based on the shapes and/orcolors.

In some implementations, the camera history timeline is displayed as ascrollable list, and the event identifiers are items in the scrollablelist (1708). The event identifiers 1322 are displayed in a scrollablelist (FIGS. 13A-13M).

In some implementations, for the respective event identifier, the alertevent indicators are ordered in accordance with a chronological order ofthe corresponding alert events (1710). The icons 1350 are ordered, whiledisplayed, based on the chronological order of the alert eventsindicated. In some implementations, the icons 1350 are ordered based onthe chronological order of the most recent instance of each alert eventtype for that camera event.

FIGS. 18A-18B illustrate a flowchart diagram of a method 1800 forpresenting a camera history in accordance with some implementations. Insome implementations, the method 1800 is performed by an electronicdevice with one or more processors, memory, a display, and optionally atouch screen, an accelerometer, and/or an audio input device. Forexample, in some implementations, the method 1800 is performed by clientdevice 504 (FIGS. 5A-5B and 8) or one or more components thereof (e.g.,client-side module 502, presentation module 821, input processing module822, web browser module 823, application 824, user interface module826). In some implementations, the method 1800 is governed byinstructions that are stored in a non-transitory computer readablestorage medium (e.g., the memory 806) and the instructions are executedby one or more processors of the electronic device (e.g., the CPUs 802).Optional operations are indicated by dashed lines (e.g., boxes withdashed-line borders).

The client device, in an application executing on the client device,displays a camera event history provided by a remote server system,where the camera event history is presented as a chronologically-orderedset of event identifiers, each event identifier corresponding to arespective event for which a remote camera has captured an associatedvideo (1802). For example, the smart home application displays, ininterface 1304, camera history information as a scrollable list ofchronologically-ordered event identifiers 1322 (which may still beviewed as a timeline, because the event identifiers are chronologicallyordered and separated by hour). The scrollable list of event identifiers1322 displayed in interface 1304 includes event identifiers 1322corresponding to respective camera events with associated video from acamera 118.

The client device receives a user selection of a displayed eventidentifier (1814). As shown in FIG. 13B, for example, the user mayperform a gesture (e.g., a single tap gesture with contact 1340) on anevent identifier 1322-E.

The client device, in response to receiving the user selection of thedisplayed event identifier, expands the selected event identifier into avideo player window, the video player window consuming a portion of thedisplayed camera event history; and plays, in the video player window,the captured video associated with the selected event identifier (1816).In response to detecting the gesture on the event identifier 1322-E, thesmart home application expands the event identifier 1322 inline into avideo player interface 1342 (FIG. 13C). The video player interface 1342consumes space in the scrollable list. The video player interface 1342includes, and plays, the video 1354 associated with the correspondingcamera event.

In some implementations, the video player window consumes only a portionof the displayed camera event history. The video player interface 1342,for example, consumes a portion of the scrollable list; other eventidentifiers (e.g., identifiers 1322-D and 1322-F, FIG. 13C) are stilldisplayed.

In some implementations, the playback of video 1354 is automaticallyinitiated when the event identifier 1322 expands into the video playerinterface 1342. In some implementations, the playback of video 1354needs to be manually initiated after the event identifier 1322 expandsinto the video player interface 1342. For example, the user manuallyactivates playback by performing a gesture on the playback affordance1364 (FIG. 13D) displayed after the event identifier 1322 expands intothe video player interface 1342.

In response to terminating playback of the captured video associatedwith the selected event identifier or user de-selection of the displayedevent identifier, the client device collapses the video player windowinto the selected event identifier thereby stopping the playing of thecaptured video associated with the selected event identifier (1818). Theuser may de-select the event identifier 1322-E by performing a gesturein the video player interface 1342 away from the video 1354 (e.g.,gesture with contact 1374 in an empty area in video player interface1342, FIG. 13E). In response to the gesture, the video player interface1342 collapses back into event identifier 1322-E and stops playback ofthe video 1354 if playback was in progress. In some implementations,additionally, when playback of the video 1354 is completed, the smarthome application automatically collapses the video player interface 1354back into event identifier 1322-E.

In some implementations, the set of event identifiers are displayed as ascrollable list of the event identifiers (1804). The event identifiers1322 are displayed in a scrollable list (FIGS. 13A-13M).

In some implementations, a respective event corresponding to thedisplayed event identifier is a non-camera event, and a video associatedwith the respective event is captured by the remote camera during thenon-camera event (1806). An event identifier 1322 may corresponding to acamera event where motion is not detected in the video itself, but oneor more non-camera alert event(s) (e.g., hazard, sound, vibration, etc.)are detected, and video associated with the camera event is capturedduring the non-camera alert event(s).

In some implementations, each event identifier has a thumbnail imageassociated with the corresponding respective event (1808). Each eventidentifier 1322 includes a thumbnail 1328, which may be a frame of theassociated video or the associated video in thumbnail-size.

In some implementations, a video associated with a respective event andcaptured by the remote camera is contemporaneous with the associatedrespective event (1810). For example, when the alert event(s) for acamera event are non-camera alert event(s), the associated video isvideo captured proximate in time with the alert event(s). Video capturedproximate in time with the alert event(s) may be captured while thealert event(s) are detected or immediately after the alert event(s) islast detected (e.g., for instantaneous alert events such as sounds).

In some implementations, a video associated with a respective event issaved at the remote server system (1812). Video associated with cameraevents are saved and stored at the hub device server system 508 or videoserver system 552 (e.g., in video storage database 7320).

In some implementations, for the displayed event identifier, the clientdevice displays one or more alert event icons, each alert event iconcorresponding to a respective alert event triggered in response to arespective event corresponding to the displayed event identifier (1820).For example, when a filter is applied, icons 1350 may be displayed inevent identifiers 1322 (FIGS. 13J-13K). The icons 1350 indicate alertevents that have been detected for the camera event corresponding to therespective event identifiers 1322.

In some implementations, within the displayed event identifier, thealert event icons are visually distinctive from each other based on iconcolor (1822). In some implementations, within the displayed eventidentifier, the alert event icons are visually distinctive from eachother based on icon shape (1824). The icons 1350 have distinctive shapesand/or colors mapped to alert event types; the user can identify thealert event types indicated by the icons 1350 based on the shapes and/orcolors.

In some implementations, within the displayed event identifier, thealert event icons are ordered in accordance with a chronological orderin which the triggered alert events were triggered in response to therespective event corresponding to the displayed event identifier (1826).Within an event identifier 1322, the icons 1350 are ordered by thechronological order of the instances of alert events to which thedisplayed icons 1350 correspond. For example, in FIG. 13K, in eventidentifier 1322-F the alert event corresponding to icon 1352-A is morerecent than the alert event corresponding to icon 1352-B.

In some implementations, the client device displays in the displayedevent identifier information regarding a most recently triggered alertevent of the triggered alert events (1828). The activity type identifier1330 of an event identifier identifies, in some implementations, thealert event type of the most recent alert event associated with thecorresponding camera event. For example, in FIG. 13M, for eventidentifier 1322-Q the alert event type of the most recent alert event is“Motion Activity” 1330-Q, whereas for event identifier 1322-R the alertevent type of the most recent alert event is “Sound Activity” 1330-R.

FIGS. 19A-19L illustrate example screenshots of user interfaces on aclient device in accordance with some implementations. In someimplementations, the user interfaces depicted in FIGS. 19A-19L are userinterfaces for a smart home application on a client device (e.g., clientdevice 504), such as a smart phone or a tablet computer.

FIG. 19A shows a home page user interface analogous to user interface1104 (FIG. 11A). The home page user interface in FIG. 19A includes auser interface element (the circular element with the label “Downstairs( . . . ” below) analogous to camera objects 1116; a video feed from acamera labeled “Downstairs (Q1)” is displayed with cropping in the userinterface element. FIG. 19B shows the home page user interface inlandscape orientation (the user interface as shown in FIG. 19A isoriented in portrait orientation). A user may activate the userinterface element (e.g., by performing a single tap gesture on it) toaccess a video feed user interface analogous to user interface 1166(FIG. 11T) for the “Downstairs (Q1)” camera.

FIG. 19C shows a video feed user interface for the “Downstairs (Q1)”camera, in portrait orientation. The video feed user interface includesa label or identifier of the camera whose video feed is being shown; adate and time of the video being shown; a live feed indicator; a cameraon/off switch, the video feed from the camera; and various controls andaffordances, including an affordance to jump to a video corresponding tothe next camera event chronologically (e.g., “Next Video,” “NextEvent”), an affordance to jump to a video corresponding to the previouscamera event chronologically (e.g., “Previous Video,” “Previous Event”),and a history affordance analogous to affordance 1190. FIG. 19D showsthe video feed user interface in landscape orientation. In landscapeorientation, the affordances and controls may be hidden by default anddisplayed when the user performs a gesture (e.g., a single tap gesture)on the displayed (playing or paused) video feed. A user may activate thehistory affordance to access a camera history user interface, analogousto user interface 1304 (FIG. 13A), for the “Downstairs (Q1)” camera.

FIG. 19E shows a camera history user interface for the “Downstairs (Q1)”camera. The camera history user interface includes a scrollable list ofcamera events, which are analogous to camera events 1322. Each cameraevent includes a time and duration of the camera event, a thumbnail ofan associated video (where the thumbnail may be a still image of a framefrom the video, periodically refreshed frames from the video, or thevideo itself playing at the thumbnail size), a label indicating an alertevent type associated with the camera event (e.g., the primary orpreeminent or dominant or longest or most recent alert event type forthe camera event), and indicators (e.g., respective icons andcorresponding labels or identifiers) of alert event types associatedwith the camera event. The indicators, in FIG. 19E, are distinct bycolor (e.g., the color for “Zone 2” is different for the color for “Zone1”). Additionally, the indicators are chronologically ordered based onthe times of occurrence for those alert event types or zones ofinterest. FIG. 19F illustrates the scrollable list scrolled to revealmore camera events and remove from display camera events that have beenscrolled off-display.

The scrollable list may be filtered to show just camera events thatsatisfy particular filtering criteria (e.g., camera events that haveparticular alert event types). FIG. 19G shows a menu, analogous tofiltering menu 1378 (FIG. 13H-13I, 13L) to select particular alert eventtypes and zones of interest for filtering. For example, in FIG. 19G,“Zone 2,” “Motion not in your activity zones,” and “Sound” are selected.FIG. 19H shows the result of the filtering in FIG. 19G, which includesany camera event that includes at least one of “Zone 2,” “Motion not inyour activity zones,” and “Sound.”

FIG. 19I shows the filtering menu with a different set of alert eventtypes and zones selected for filtering. The user may select or deselectthe listed zones and alert event types to filter by the selected zonesand alert event types. In FIG. 19I, “Motion not in your activity zones”and “Sound” are selected. FIG. 19J shows the result of the filtering inFIG. 19I, which includes any camera event that includes at least one of“Motion not in your activity zones” and “Sound.” No camera event hasthese alert event types, and thus no camera events are included in FIG.19J. Instead, a message indicating that there are no camera eventssatisfying the filtering criteria is displayed.

FIG. 19K shows the result of selecting a camera event from thescrollable list (e.g., by performing a single tap gesture on the cameraevent). The camera event expands, inline in the scrollable list, into avideo player interface analogous to video play interface 1342 (FIG.13C). In the video player interface, the video associated with theselected camera event is played; playback is started automatically. Thevideo player interface continues to show the chronologically ordered andcolor-distinct indicators of alert event types and zones of interestassociated with the camera event.

FIG. 19L shows the video in the video player interface having finishedplaying. A “Replay” affordance and a “Continue” affordance aredisplayed. The user may activate the “Replay” affordance to replay thevideo. Or, the user may activate the “Continue” affordance to access thevideo feed user interface for the associated camera (FIG. 19C or 19D,depending on the device orientation). In the video feed user interface,in some implementations, the video feed is played from the end of thevideo that ended playback in the video player interface. In some otherimplementations, the next saved video clip for the camera is played.

FIGS. 20A-20M illustrate example screenshots of user interfaces on aclient device in accordance with some implementations. In someimplementations, the user interfaces depicted in FIGS. 20A-20M are userinterfaces for managing a smart home environment (e.g., smart homeenvironment 100), displayed in one or more web pages in a web browser ona client device (e.g., client device 504), such as a desktop or laptopcomputer.

FIG. 20A shows a home page user interface analogous to user interface1104 (FIG. 11A). The home page user interface in FIG. 20A includes auser interface element (the circular element with the label “Downstairs(Q1)” below) analogous to camera objects 1116; a video feed from acamera labeled “Downstairs (Q1)” is displayed with cropping in the userinterface element. A user may activate the user interface element (e.g.,by clicking on the user interface element) to access a video feed userinterface analogous to user interface 1204 (FIG. 12A) for the“Downstairs (Q1)” camera.

FIG. 20B shows a video feed user interface for the “Downstairs (Q1)”camera. The video feed user interface includes a label or identifier ofthe camera whose video feed is being shown; a date and time of the videobeing shown; a live feed indicator; a camera on/off switch, the videofeed from the camera; various affordances, including an affordance toselect a date, an affordance to access a zone filtering/editing menu(analogous to affordance 1229, FIG. 12A), a timeline, and affordance(s)to change the time interval scaling in the timeline. FIG. 20B shows thetimeline at the minutes scale. FIG. 20C shows the timeline at theseconds scale. FIG. 20D shows the timeline at the hours scale. A cameraevent is displayed on the timeline as a bar or a dot in accordance withits duration and the scale of the timeline. The length of the bar/dotindicates the duration of the camera event; a camera event of sufficientduration “stretches” the dot into a bar in accordance with the timescale of the timeline. In FIGS. 20B and 20D, camera events are displayedas dots on the timeline, while in FIG. 20C there are no camera eventsdisplayed on the timeline for the time range shown (e.g., because thereare no camera events for that time range).

In some implementations, additional controls and affordances aredisplayed when a mouse pointer is hovered over the video. For example,FIG. 20E shows the additional controls and affordances displayed. Theadditional controls and affordances include, for example zoomingcontrols, a pause button, buttons to jump forward or backward by apredefined amount of time, a button to jump to the current live videofeed, a volume control, and a button to expand the video to full-screen.In some implementations, the controls and affordances include, inaddition to or in lieu of the buttons to jump forward or backward by apredefined amount of time, a button to jump forward to a videocorresponding to the next camera event chronologically (e.g., “NextVideo,” “Next Event”) and/or a button jump backward to a videocorresponding to the previous camera event chronologically (e.g.,“Previous Video,” “Previous Event”).

FIG. 20F shows a zone filtering/editing menu displayed in response toactivation of the affordance to access the zone filtering/editing menu.The user may select or deselect the listed zones and alert event typesto filter by the selected zones and alert event types. In the zonefiltering/editing menu, there are also options to edit an existinguser-defined zone of interest (e.g., “Zone 1” listed in the zonefiltering/editing menu) and an option to create a new user-defined zoneof interest. In FIG. 20F, the existing zones are displayed over thevideo in response to activation of the option to edit a zone ofinterest. The zones are displayed as bounded areas with respectiveboundaries and boundary handles. The zones are displayed so that theuser may select the zone to be edited by clicking on the displayed zone.If there are multiple zones of interest, in some implementations, theyare displayed with different colors (e.g., one zone, and itscorresponding boundary, handles, and area, is displayed in yellow;another zone is displayed in blue; and so on).

FIG. 20H shows filtering of the timeline. In FIG. 20H, “Zone 1” isselected in the zone filtering/editing menu, and “Motion not in youractivity zones” and “Sound” are deselected. No camera events aredisplayed in the timeline, at last for the time range shown in thetimeline, as there are no camera events in the shown time range that isassociated with motion detected in “Zone 1.”

FIG. 20I also shows filtering of the timeline. In FIG. 20I, “Motion notin your activity zones” is selected in the zone filtering/editing menu,and “Zone 1” and “Sound” are deselected. Camera events that includedetected motion not in any user-defined zone are displayed in thetimeline.

FIG. 20J shows a camera event displayed as a bar on the timeline, withtwo colored dots in the bar. The colored dots correspond to respectivezones or alert event types associated with the camera event. The coloreddots have different colors, each respective color being associated witha respective user-defined zone or alert event type. In someimplementations, each user-defined zone and alert event type isassociated with a distinct color. In some other implementations, eachuser-defined zone is associated with a distinct color, and one or moreof the alert event types that are not user-defined zones are associatedwith a color distinct from the colors for the user-defined zones. Insome implementations, the colored dots are chronologically orderedwithin the bar in accordance with the times of occurrence of thecorresponding alert events.

FIG. 20K shows an information pop-up displayed in response to a userclicking on (e.g., with a mouse) or tapping on (e.g., with a contact ona touch screen) or hovering over (e.g., with a mouse pointer) the cameraevent bar. The information pop-up (analogous to information pop-up 1242,FIG. 12B) includes a thumbnail of the video associated with the cameraevent; date and time information for the camera event; and colored dotsthat repeat the differently-colored dots displayed in the camera eventbar.

FIGS. 20L and 20M show another example of a camera event bar and aninformation pop-up. In FIGS. 20L and 20M, the differently-colored dotsin the camera event bar have a different order than in FIGS. 20J-20K,indicating that the chronology of the alert events/motion detected inzones are different in the two camera events.

For situations in which the systems discussed above collect informationabout users, the users may be provided with an opportunity to opt in/outof programs or features that may collect personal information (e.g.,information about a user's preferences or usage of a smart device). Inaddition, in some implementations, certain data may be anonymized in oneor more ways before it is stored or used, so that personallyidentifiable information is removed. For example, a user's identity maybe anonymized so that the personally identifiable information cannot bedetermined for or associated with the user, and so that user preferencesor user interactions are generalized (for example, generalized based onuser demographics) rather than associated with a particular user.

Although some of various drawings illustrate a number of logical stagesin a particular order, stages that are not order dependent may bereordered and other stages may be combined or broken out. While somereordering or other groupings are specifically mentioned, others will beobvious to those of ordinary skill in the art, so the ordering andgroupings presented herein are not an exhaustive list of alternatives.Moreover, it should be recognized that the stages could be implementedin hardware, firmware, software or any combination thereof.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific implementations. However, theillustrative discussions above are not intended to be exhaustive or tolimit the scope of the claims to the precise forms disclosed. Manymodifications and variations are possible in view of the aboveteachings. The implementations were chosen in order to best explain theprinciples underlying the claims and their practical applications, tothereby enable others skilled in the art to best use the implementationswith various modifications as are suited to the particular usescontemplated.

1. (canceled)
 2. A method comprising: obtaining, by a computing device,alert events from one or more smart devices at a physical location, theone or more smart devices including a camera located at or in proximityto the physical location, wherein each obtained alert event isassociated with at least one of a plurality of predefined activity alerttypes; outputting, for display at a display screen of the computingdevice, a camera history user interface that includes a scrollable listof a plurality of camera event items from the camera that are arrangedin a chronological sequence and a filter graphical element, wherein eachof the camera event items in the scrollable list is displayed across afull width of the scrollable list and including an image, a time of analert event associated with the respective camera event item, and one ormore activity alert indicators corresponding to one or more of thepredefined activity alert types; detecting, by the computing device, auser input at a location of the display at which the filter graphicalelement is displayed; responsive to detecting the user input,outputting, by the computing device and for display, a filtering menuthat includes one or more filtering criteria; receiving, by thecomputing device, a selection of a filtering criteria from the one ormore filtering criteria; determining, by the computing device and basedon the filtering criteria, a subset of camera event items from theplurality of camera event items; and outputting, for display, an updatedcamera history user interface that includes a scrollable list of thesubset of camera event items.
 3. The method of claim 2, wherein thefiltering criteria include one or more of a zone of interest, a soundalert event type, a vibration alert event type, a hazard alert eventtype, or a motion alert event type.
 4. The method of claim 2, whereinoutputting the filtering menu further comprises: obscuring the camerahistory user interface; and outputting the filtering menu for displayover a portion of the obscured camera history user interface.
 5. Themethod of claim 2, wherein the selection of the filtering criteria is aselection of a first filtering criteria, and wherein the one or morefiltering criteria include at least two filtering criteria, the methodfurther comprising: receiving, by the computing device, a selection of asecond filtering criteria from the at least two filtering criteria,wherein determining the subset of camera event items is based on thefirst filtering criteria and the second filtering criteria.
 6. Themethod of claim 2, wherein the predefined activity alert types areassociated with one or more of a hazard alert event, an audio alertevent, a motion alert event in a zone of interest in a field of view ofthe camera, or a motion event outside of the zone of interest in thefield of view of the camera; and the zone of interest comprises adefined spatial zone in the field of view.
 7. The method of claim 6,wherein the spatial zone is defined by a user.
 8. The method of claim 2,wherein each of the one or more activity alert indicators has a visuallydistinctive display characteristic based on color or shape.
 9. Themethod of claim 2, wherein the full width of the scrollable list is afull width of the display screen.
 10. A computing device comprising: adisplay screen; one or more processors; and a memory storinginstructions that, when executed by the one or more processors cause theone or more processors to: obtain alert events from one or more smartdevices at a physical location, the one or more smart devices includinga camera located at or in proximity to the physical location, whereineach obtained alert event is associated with at least one of a pluralityof predefined activity alert types; output, for display at the displayscreen, a camera history user interface that includes a scrollable listof a plurality of camera event items from the camera that are arrangedin a chronological sequence and a filter graphical element, wherein eachof the camera event items in the scrollable list is displayed across afull width of the scrollable list and including an image, a time of analert event associated with the respective camera event item, and one ormore activity alert indicators corresponding to one or more of thepredefined activity alert types; detect a user input at a location ofthe display screen at which the filter graphical element is displayed;responsive to detecting the user input, output, for display, a filteringmenu that includes one or more filtering criteria; receive a selectionof a filtering criteria from the one or more filtering criteria;determine, based on the filtering criteria, a subset of camera eventitems from the plurality of camera event items; and output, for display,an updated camera history user interface that includes a scrollable listof the subset of camera event items.
 11. The computing device of claim10, wherein the filtering criteria include one or more of a zone ofinterest, a sound alert event type, a vibration alert event type, ahazard alert event type, or a motion alert event type.
 12. The computingdevice of claim 10, wherein the instructions further cause the one ormore processors to: obscure the camera history user interface; andoutput the filtering menu for display over a portion of the obscuredcamera history user interface.
 13. The computing device of claim 10,wherein the selection of the filtering criteria is a selection of afirst filtering criteria, wherein the one or more filtering criteriainclude at least two filtering criteria, and wherein the instructionsfurther cause the one or more processors to: receive a selection of asecond filtering criteria from the at least two filtering criteria; anddetermine the subset of camera event items based on the first filteringcriteria and the second filtering criteria.
 14. The computing device ofclaim 10, wherein the predefined activity alert types are associatedwith one or more of a hazard alert event, an audio alert event, a motionalert event in a zone of interest in a field of view of the camera, or amotion event outside of the zone of interest in the field of view of thecamera; and the zone of interest comprises a defined spatial zone in thefield of view.
 15. The computing device of claim 14, wherein the spatialzone is defined by a user.
 16. The computing device of claim 10, whereineach of the one or more activity alert indicators has a visuallydistinctive display characteristic based on color or shape.
 17. Thecomputing device of claim 10, wherein the full width of the scrollablelist is a full width of the display screen.
 18. A non-transitorycomputer-readable storage medium encoded with instructions that, whenexecuted by one or more processors of a computing device, cause the oneor more processors to: obtain alert events from one or more smartdevices at a physical location, the one or more smart devices includinga camera located at or in proximity to the physical location, whereineach obtained alert event is associated with at least one of a pluralityof predefined activity alert types; output, for display at a displayscreen of the computing device, a camera history user interface thatincludes a scrollable list of a plurality of camera event items from thecamera that are arranged in a chronological sequence and a filtergraphical element, wherein each of the camera event items in thescrollable list is displayed across a full width of the scrollable listand including an image, a time of an alert event associated with therespective camera event item, and one or more activity alert indicatorscorresponding to one or more of the predefined activity alert types;detect a user input at a location of the display at which the filtergraphical element is displayed; responsive to detecting the user input,output, for display, a filtering menu that includes one or morefiltering criteria; receive a selection of a filtering criteria from theone or more filtering criteria; determine, based on the filteringcriteria, a subset of camera event items from the plurality of cameraevent items; and output, for display, an updated camera history userinterface that includes a scrollable list of the subset of camera eventitems.
 19. The non-transitory computer-readable storage medium of claim18, wherein the instructions further cause the one or more processorsto: obscure the camera history user interface; and output the filteringmenu for display over a portion of the obscured camera history userinterface.
 20. The non-transitory computer-readable storage medium ofclaim 18, wherein the selection of the filtering criteria is a selectionof a first filtering criteria, wherein the one or more filteringcriteria include at least two filtering criteria, and wherein theinstructions further cause the one or more processors to: receive aselection of a second filtering criteria from the at least two filteringcriteria; and determine the subset of camera event items based on thefirst filtering criteria and the second filtering criteria.
 21. Thenon-transitory computer-readable storage medium of claim 18, wherein thefiltering criteria include one or more of a zone of interest, a soundalert event type, a vibration alert event type, a hazard alert eventtype, or a motion alert event type.